MAN page from OpenSuSE cargo-1.36.0-lp151.5.8.1.i586.rpm

CARGO\-FETCH

Section: \ \& (1)
Updated: 2019-05-12
Index

NAME

cargo-fetch - Fetch dependencies of a package from the network

SYNOPSIS

cargo fetch [OPTIONS]

DESCRIPTION

If a Cargo.lock file is available, this command will ensure that all of thegit dependencies and/or registry dependencies are downloaded and locallyavailable. Subsequent Cargo commands never touch the network after a cargofetch unless the lock file changes.

If the lock file is not available, then this command will generate the lockfile before fetching the dependencies.

If --target is not specified, then all target dependencies are fetched.

See also the https://crates.io/crates/cargo-prefetch <L>cargo-prefetchplugin which adds a command to download popular crates. This may be useful ifyou plan to use Cargo without a network with the --offline flag.

OPTIONS

Fetch options

--target TRIPLE

: Fetch for the given architecture. The default is the hostarchitecture. The general format of the triple is<arch><sub>-<vendor>-<sys>-<abi>. Run rustc --print target-list for alist of supported targets.
This may also be specified with the build.targethttps://doc.rust-lang.org/cargo/reference/config.html <L>config value

Display Options

-v, --verbose

: Use verbose output. May be specified twice for "very verbose" output whichincludes extra output such as dependency warnings and build script output.May also be specified with the term.verbosehttps://doc.rust-lang.org/cargo/reference/config.html <L>config value

-q, --quiet

: No output printed to stdout.

--color WHEN

Control when colored output is used. Valid values:

: *auto (default): Automatically detect if color support is available on theterminal.

: *always: Always display colors.

: *never: Never display colors.

May also be specified with the term.colorhttps://doc.rust-lang.org/cargo/reference/config.html <L>config value

Manifest Options

--manifest-path PATH

: Path to the Cargo.toml file. By default, Cargo searches in the currentdirectory or any parent directory for the Cargo.toml file.

--frozen, --locked

: Either of these flags requires that the Cargo.lock file isup-to-date. If the lock file is missing, or it needs to be updated, Cargo willexit with an error. The --frozen flag also prevents Cargo fromattempting to access the network to determine if it is out-of-date.
These may be used in environments where you want to assert that theCargo.lock file is up-to-date (such as a CI build) or want to avoid networkaccess.

--offline

Prevents Cargo from accessing the network for any reason. Without thisflag, Cargo will stop with an error if it needs to access the network andthe network is not available. With this flag, Cargo will attempt toproceed without the network if possible.

Beware that this may result in different dependency resolution than onlinemode. Cargo will restrict itself to crates that are downloaded locally, evenif 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 goingoffline.

May also be specified with the net.offline https://doc.rust-lang.org/cargo/reference/config.html <L>config value