cargo-vendor - Vendor all dependencies locally
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.
- -s MANIFEST
- --sync MANIFEST
-
Specify extra
Cargo.tomlmanifests to workspaces which should also be vendored and synced to the output. - --no-delete
-
Don’t delete the "vendor" directory when vendoring, but rather keep all existing contents of the vendor directory
- --respect-source-config
-
Instead of ignoring
[source]configuration by default in.cargo/configread it and use it when downloading crates from crates.io, for example - --versioned-dirs
-
Normally versions are only added to disambiguate multiple versions of the same package. This option causes all directories in the "vendor" directory to be versioned, which makes it easier to track the history of vendored packages over time, and can help with the performance of re-vendoring when only a subset of the packages have changed.
-
Vendor all dependencies into a local "vendor" folder
cargo vendor
-
Vendor all dependencies into a local "third-party/vendor" folder
cargo vendor third-party/vendor
-
Vendor the current workspace as well as another to "vendor"
cargo vendor -s ../path/to/Cargo.toml