mirror of
https://github.com/rust-lang/cargo.git
synced 2025-09-28 11:20:36 +00:00
033e06a1cc
This came from #12638 and my many small frustrations from wanting to use `-n` and not being able to. We do not have any existing `-n` flags for this to be confused with. I would wager that `-n` is such an entrenched short flag in build tools that it would not make sense for us to use it with any other flag. For a survey of where `-n` is used as a short, see https://www.gnu.org/prep/standards/html_node/Option-Table.html#Option-Table
27 lines
1.1 KiB
Plaintext
27 lines
1.1 KiB
Plaintext
Update dependencies as recorded in the local lock file
|
|
|
|
Usage: cargo[EXE] update [OPTIONS] [SPEC]...
|
|
|
|
Options:
|
|
-n, --dry-run Don't actually write the lockfile
|
|
--recursive Force updating all dependencies of [SPEC]... as well
|
|
--precise <PRECISE> Update [SPEC] to exactly PRECISE
|
|
-q, --quiet Do not print cargo log messages
|
|
-v, --verbose... Use verbose output (-vv very verbose/build.rs output)
|
|
--color <WHEN> Coloring: auto, always, never
|
|
--config <KEY=VALUE> Override a configuration value
|
|
-Z <FLAG> Unstable (nightly-only) flags to Cargo, see 'cargo -Z help' for details
|
|
-h, --help Print help
|
|
|
|
Package Selection:
|
|
-w, --workspace Only update the workspace packages
|
|
[SPEC]... Package to update
|
|
|
|
Manifest Options:
|
|
--manifest-path <PATH> Path to Cargo.toml
|
|
--frozen Require Cargo.lock and cache are up to date
|
|
--locked Require Cargo.lock is up to date
|
|
--offline Run without accessing the network
|
|
|
|
Run `cargo help update` for more detailed information.
|