0fa9ad8673
rustpkg can now build code from a local git repository. In the case where the local repo is in a directory not in the RUST_PATH, it checks out the repository into a directory in the first workspace in the RUST_PATH. The tests no longer try to connect to github.com, which should solve some of the sporadic failures we've been seeing. |
||
|---|---|---|
| .. | ||
| testsuite | ||
| api.rs | ||
| conditions.rs | ||
| context.rs | ||
| crate.rs | ||
| installed_packages.rs | ||
| messages.rs | ||
| package_id.rs | ||
| package_path.rs | ||
| package_source.rs | ||
| path_util.rs | ||
| README.txt | ||
| rustpkg.rs | ||
| search.rs | ||
| source_control.rs | ||
| target.rs | ||
| tests.rs | ||
| usage.rs | ||
| util.rs | ||
| version.rs | ||
| workspace.rs | ||
Right now, commands that work are "build" and "clean".
`rustpkg build` and `rustpkg clean` should work
for example:
$ cd ~/rust/src/librustpkg/testsuite/pass
$ rustpkg build hello-world
... some output ...
$ rustpkg clean hello-world
-------------
the following test packages in librustpkg/testsuite/pass:
* hello-world
* install-paths
* simple-lib
* deeply/nested/path
* fancy-lib
It fails on the following test packages:
* external-crate (no support for `extern mod` inference yet)
and should fail with proper error messages
on all of the test packages in librustpkg/testsuite/fail
* no-inferred-crates