table of contents
CARGO-VENDOR(1) | CARGO-VENDOR(1) |
NAME¶
cargo-vendor - Vendor all dependencies locallySYNOPSIS¶
cargo vendor [OPTIONS] [PATH]DESCRIPTION¶
This cargo subcommand will vendor all crates.io and git dependencies for a project into the specified directory at <path>. After this command completes the vendor directory specified by <path> will contain all remote sources from dependencies specified. Additional manifests beyond the default one can be specified with the -s option.The cargo vendor command will also print out the configuration necessary to use the vendored sources, which you will need to add to .cargo/config.
OPTIONS¶
Owner Options¶
-s MANIFEST, --sync MANIFEST--no-delete
--respect-source-config
--versioned-dirs
Manifest Options¶
--manifest-path PATHDisplay Options¶
-v, --verbose-q, --quiet
--color WHEN
May also be specified with the term.color config value <https://doc.rust-lang.org/cargo/reference/config.html>.
Common Options¶
-h, --help-Z FLAG...
--frozen, --locked
These may be used in environments where you want to assert that the Cargo.lock file is up-to-date (such as a CI build) or want to avoid network access.
--offline
Beware that this may result in different dependency resolution than online mode. Cargo will restrict itself to crates that are downloaded locally, even if there might be a newer version as indicated in the local copy of the index. See the cargo-fetch(1) command to download dependencies before going offline.
May also be specified with the net.offline config value <https://doc.rust-lang.org/cargo/reference/config.html>.
ENVIRONMENT¶
See the reference <https://doc.rust-lang.org/cargo/reference/environment-variables.html> for details on environment variables that Cargo reads.EXIT STATUS¶
0101
EXAMPLES¶
cargo vendor
cargo vendor third-party/vendor
cargo vendor -s ../path/to/Cargo.toml
SEE ALSO¶
cargo(1)2019-12-09 |