rust
/
cargo
mirror of https://github.com/rust-lang/cargo
0
0
Fork 0
Code Issues Releases Wiki Activity
cargo/Cargo.toml

52 lines
998 B
TOML
Raw Normal View History

Bootstrap cargo with cargo
2014-07-16 00:51:49 +00:00
[project]
name = "cargo"
version = "0.0.1-pre"
authors = ["Yehuda Katz <wycats@gmail.com>",
"Carl Lerche <me@carllerche.com>"]
Register new snapshots
2014-08-16 20:00:46 +00:00
[lib]
Bootstrap cargo with cargo
2014-07-16 00:51:49 +00:00
name = "cargo"
path = "src/cargo/lib.rs"
Move from hammer to docopt for option parsing The hammer library currently has some shortcomings such as the inability to document individual options. Additionally our handling with hammer of extra arguments is dodgy at best currently. This commit moves the repository to BurntSushi's docopt.rs library which seems to more feature-complete at this time. Additionally, docopt has the great benefit of a "document once, use everywhere" documentation strategy. This migration solves two primary issues: * Comprehensive and useful CLI documentation * Gracefully handling flavorful combinations of arguments in odd combinations Closes #218
2014-07-24 19:43:10 +00:00
[dependencies.docopt]
Switch the location of the docopt repo
2014-09-10 05:01:39 +00:00
git = "https://github.com/docopt/docopt.rs"
Move from hammer to docopt for option parsing The hammer library currently has some shortcomings such as the inability to document individual options. Additionally our handling with hammer of extra arguments is dodgy at best currently. This commit moves the repository to BurntSushi's docopt.rs library which seems to more feature-complete at this time. Additionally, docopt has the great benefit of a "document once, use everywhere" documentation strategy. This migration solves two primary issues: * Comprehensive and useful CLI documentation * Gracefully handling flavorful combinations of arguments in odd combinations Closes #218
2014-07-24 19:43:10 +00:00
Bootstrap cargo with cargo
2014-07-16 00:51:49 +00:00
[dependencies.toml]
git = "https://github.com/alexcrichton/toml-rs"
Revert "Revert "Use libgit2 for driving git instead of the CLI"" This reverts commit 04440bb035082d4163f2211af447b8d67e077ccb. Conflicts: src/cargo/sources/git/utils.rs
2014-08-26 17:36:11 +00:00
[dev-dependencies.hamcrest]
Bootstrap cargo with cargo
2014-07-16 00:51:49 +00:00
git = "https://github.com/carllerche/hamcrest-rust.git"
Migrate from liburl to rust-url The standard url library is soon-to-be deprecated, and now that we're bootstrapping it's trivial to move over to rust-url. Closes #204
2014-07-30 16:52:37 +00:00
[dependencies.url]
git = "https://github.com/servo/rust-url"
Fix the build. After an upstream fix in docopt, cargo now builds on rust HEAD. Also, move to the semver crate rather than the deprecated built-in one.
2014-08-02 01:56:12 +00:00
[dependencies.semver]
git = "https://github.com/rust-lang/semver"
Migrate from liburl to rust-url The standard url library is soon-to-be deprecated, and now that we're bootstrapping it's trivial to move over to rust-url. Closes #204
2014-07-30 16:52:37 +00:00
Implement a registry source # cargo upload The cargo-upload command will take the local package and upload it to the specified registry. The local package is uploaded as a tarball compressed with gzip under maximum compression. Most of this is done by just delegating to `cargo package` The host to upload to is specified, in order of priority, by a command line `--host` flag, the `registry.host` config key, and then the default registry. The default registry is still `example.com` The registry itself is still a work in progress, but the general plumbing for a command such as this would look like: 1. Ensure the local package has been compressed into an archive. 2. Fetch the relevant registry and login token from config files. 3. Ensure all dependencies for a package are listed as coming from the same registry. 4. Upload the archive to the registry with the login token. 5. The registry will verify the package is under 2MB (configurable). 6. The registry will upload the archive to S3, calculating a checksum in the process. 7. The registry will add an entry to the registry's index (a git repository). The entry will include the name of the package, the version uploaded, the checksum of the upload, and then the list of dependencies (name/version req) 8. The local `cargo upload` command will succeed. # cargo login Uploading requires a token from the api server, and this token follows the same config chain for the host except that there is no fallback. To implement login, the `cargo login` command is used. With 0 arguments, the command will request that a site be visited for a login token, and with an argument it will set the argument as the new login token. The `util::config` module was modified to allow writing configuration as well as reading it. The support is a little lacking in that comments are blown away, but the support is there at least. # RegistrySource An implementation of `RegistrySource` has been created (deleting the old `DummyRegistrySource`). This implementation only needs a URL to be constructed, and it is assumed that the URL is running an instance of the cargo registry. ## RegistrySource::update Currently this will unconditionally update the registry's index (a git repository). Tuning is necessary to prevent updating the index each time (more coming soon). ## RegistrySource::query This is called in the resolve phase of cargo. This function is given a dependency to query for, and the source will simply look into the index to see if any package with the name is present. If found, the package's index file will be loaded and parsed into a list of summaries. The main optimization of this function is to not require the entire registry to ever be resident in memory. Instead, only necessary packages are loaded into memory and parsed. ## RegistrySource::download This is also called during the resolve phase of cargo, but only when a package has been selected to be built (actually resolved). This phase of the source will actually download and unpack the tarball for the package. Currently a configuration file is located in the root of a registry's index describing the root url to download packages from. This function is optimized for two different metrics: 1. If a tarball is downloaded, it is not downloaded again. It is assumed that once a tarball is successfully downloaded it will never change. 2. If the unpacking destination has a `.cargo-ok` file, it is assumed that the unpacking has already occurred and does not need to happen again. With these in place, a rebuild should take almost no time at all. ## RegistrySource::get This function is simply implemented in terms of a PathSource's `get` function by creating a `PathSource` for all unpacked tarballs as part of the `download` stage. ## Filesystem layout There are a few new directories as part of the `.cargo` home folder: * `.cargo/registry/index/$hostname-$hash` - This is the directory containing the actual index of the registry. `$hostname` comes from its url, and `$hash` is the hash of the entire url. * `.cargo/registry/cache/$hostname-$hash/$pkg-$vers.tar.gz` - This is a directory used to cache the downloads of packages from the registry. * `.cargo/registry/src/$hostname-$hash/$pkg-$vers` - This is the location of the unpacked packages. They will be compiled from this location. # New Dependencies Cargo has picked up a new dependency on the `curl-rust` package in order to send HTTP requests to the registry as well as send HTTP requests to download tarballs.
2014-07-18 15:40:45 +00:00
[dependencies.curl]
Use a different curl-rust for now Waiting on fixes to be merged upstream
2014-09-09 14:41:20 +00:00
git = "https://github.com/alexcrichton/curl-rust"
branch = "bundle"
Implement a registry source # cargo upload The cargo-upload command will take the local package and upload it to the specified registry. The local package is uploaded as a tarball compressed with gzip under maximum compression. Most of this is done by just delegating to `cargo package` The host to upload to is specified, in order of priority, by a command line `--host` flag, the `registry.host` config key, and then the default registry. The default registry is still `example.com` The registry itself is still a work in progress, but the general plumbing for a command such as this would look like: 1. Ensure the local package has been compressed into an archive. 2. Fetch the relevant registry and login token from config files. 3. Ensure all dependencies for a package are listed as coming from the same registry. 4. Upload the archive to the registry with the login token. 5. The registry will verify the package is under 2MB (configurable). 6. The registry will upload the archive to S3, calculating a checksum in the process. 7. The registry will add an entry to the registry's index (a git repository). The entry will include the name of the package, the version uploaded, the checksum of the upload, and then the list of dependencies (name/version req) 8. The local `cargo upload` command will succeed. # cargo login Uploading requires a token from the api server, and this token follows the same config chain for the host except that there is no fallback. To implement login, the `cargo login` command is used. With 0 arguments, the command will request that a site be visited for a login token, and with an argument it will set the argument as the new login token. The `util::config` module was modified to allow writing configuration as well as reading it. The support is a little lacking in that comments are blown away, but the support is there at least. # RegistrySource An implementation of `RegistrySource` has been created (deleting the old `DummyRegistrySource`). This implementation only needs a URL to be constructed, and it is assumed that the URL is running an instance of the cargo registry. ## RegistrySource::update Currently this will unconditionally update the registry's index (a git repository). Tuning is necessary to prevent updating the index each time (more coming soon). ## RegistrySource::query This is called in the resolve phase of cargo. This function is given a dependency to query for, and the source will simply look into the index to see if any package with the name is present. If found, the package's index file will be loaded and parsed into a list of summaries. The main optimization of this function is to not require the entire registry to ever be resident in memory. Instead, only necessary packages are loaded into memory and parsed. ## RegistrySource::download This is also called during the resolve phase of cargo, but only when a package has been selected to be built (actually resolved). This phase of the source will actually download and unpack the tarball for the package. Currently a configuration file is located in the root of a registry's index describing the root url to download packages from. This function is optimized for two different metrics: 1. If a tarball is downloaded, it is not downloaded again. It is assumed that once a tarball is successfully downloaded it will never change. 2. If the unpacking destination has a `.cargo-ok` file, it is assumed that the unpacking has already occurred and does not need to happen again. With these in place, a rebuild should take almost no time at all. ## RegistrySource::get This function is simply implemented in terms of a PathSource's `get` function by creating a `PathSource` for all unpacked tarballs as part of the `download` stage. ## Filesystem layout There are a few new directories as part of the `.cargo` home folder: * `.cargo/registry/index/$hostname-$hash` - This is the directory containing the actual index of the registry. `$hostname` comes from its url, and `$hash` is the hash of the entire url. * `.cargo/registry/cache/$hostname-$hash/$pkg-$vers.tar.gz` - This is a directory used to cache the downloads of packages from the registry. * `.cargo/registry/src/$hostname-$hash/$pkg-$vers` - This is the location of the unpacked packages. They will be compiled from this location. # New Dependencies Cargo has picked up a new dependency on the `curl-rust` package in order to send HTTP requests to the registry as well as send HTTP requests to download tarballs.
2014-07-18 15:40:45 +00:00
Implement cargo-package This command will assemble the current package into a tarball ready for uploading to the cargo registry. Currently no further verification is done beyond packaging the local repository into a tarball, but in the future this could execute other operations such as api stability tools.
2014-07-18 15:40:45 +00:00
[dependencies.tar]
git = "https://github.com/alexcrichton/tar-rs"
[dependencies.flate2]
git = "https://github.com/alexcrichton/flate2-rs"
Revert "Revert "Use libgit2 for driving git instead of the CLI"" This reverts commit 04440bb035082d4163f2211af447b8d67e077ccb. Conflicts: src/cargo/sources/git/utils.rs
2014-08-26 17:36:11 +00:00
[dependencies.git2]
git = "https://github.com/alexcrichton/git2-rs"
Fix building with current rust by using rust-lang/glob The glob crate that comes with rust itself has been deprecated.
2014-08-27 10:49:11 +00:00
[dependencies.glob]
git = "https://github.com/rust-lang/glob"
Bootstrap cargo with cargo
2014-07-16 00:51:49 +00:00
[[bin]]
name = "cargo"
test = false
Remove docs that shouldn't be built
2014-08-14 21:54:56 +00:00
doc = false
Bootstrap cargo with cargo
2014-07-16 00:51:49 +00:00
[[test]]
name = "tests"
Implement resolution of version requirements This commit extends the support in cargo's resolver to start resolving packages with multiple versions as well as package requirements. This is a crucial step forward when impelmenting the cargo registry as multiple versions will be uploaded to the registry quite quickly! This implements a fairly naive solution which should at least help cargo get out the gates initially. This impelments a depth-first-search of the pacakage dependency graph with a few sorting heuristics along the way to help out resolution as it goes along. Resolution errors will likely improve over time, but this commit does make an effort to try to get some good error messages right off the bat.
2014-10-17 15:17:17 +00:00
[[test]]
name = "resolve"