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

Auto merge of #13665 - weihanglo:locked-frozen, r=<try> 

docs: clarify `--locked` ensures Cargo uses dependency versions in lockfile
This commit is contained in:
bors 2024-03-28 03:23:28 +00:00
parent 07253b7ea6 0233632b0c
commit 9d3403ad85
109 changed files with 1242 additions and 707 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
src/bin/cargo/cli.rs
View File

@ -640,12 +640,7 @@ See '<cyan,bold>cargo help</> <cyan><<command>></>' for more information on a sp
.value_parser(clap::builder::ValueParser::path_buf()),
)
.arg(
flag("frozen", "Require Cargo.lock and cache to be up-to-date")
.help_heading(heading::MANIFEST_OPTIONS)
.global(true),
)
.arg(
flag("locked", "Require Cargo.lock to be up-to-date")
flag("locked", "Ensure the exact dependency versions in Cargo.lock is used")
.help_heading(heading::MANIFEST_OPTIONS)
.global(true),
)
@ -654,6 +649,11 @@ See '<cyan,bold>cargo help</> <cyan><<command>></>' for more information on a sp
.help_heading(heading::MANIFEST_OPTIONS)
.global(true),
)
.arg(
flag("frozen", "Equivalent to specifying both --locked and --offline")
.help_heading(heading::MANIFEST_OPTIONS)
.global(true),
)
// Better suggestion for the unsupported short config flag.
.arg( Arg::new("unsupported-short-config-flag")
.help("")

24
src/doc/man/generated_txt/cargo-add.txt
View File

@ -171,16 +171,19 @@ OPTIONS
-p spec, --package spec
Add dependencies to only the specified package.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -197,6 +200,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/generated_txt/cargo-bench.txt
View File

@ -338,16 +338,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -364,6 +367,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/generated_txt/cargo-build.txt
View File

@ -272,16 +272,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -298,6 +301,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/generated_txt/cargo-check.txt
View File

@ -257,16 +257,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -283,6 +286,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/generated_txt/cargo-clean.txt
View File

@ -91,16 +91,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -117,6 +120,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/generated_txt/cargo-doc.txt
View File

@ -228,16 +228,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -254,6 +257,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/generated_txt/cargo-fetch.txt
View File

@ -71,16 +71,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -96,6 +99,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/generated_txt/cargo-fix.txt
View File

@ -330,16 +330,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -356,6 +359,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/generated_txt/cargo-generate-lockfile.txt
View File

@ -46,16 +46,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -72,6 +75,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/generated_txt/cargo-install.txt
View File

@ -242,16 +242,19 @@ OPTIONS
machine-readable JSON information about timing information.
Manifest Options
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -268,6 +271,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Miscellaneous Options
-j N, --jobs N
Number of parallel jobs to run. May also be specified with the

24
src/doc/man/generated_txt/cargo-metadata.txt
View File

@ -404,16 +404,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -430,6 +433,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/generated_txt/cargo-package.txt
View File

@ -158,16 +158,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -184,6 +187,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Miscellaneous Options
-j N, --jobs N
Number of parallel jobs to run. May also be specified with the

24
src/doc/man/generated_txt/cargo-pkgid.txt
View File

@ -84,16 +84,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -110,6 +113,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/generated_txt/cargo-publish.txt
View File

@ -128,16 +128,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -154,6 +157,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Miscellaneous Options
-j N, --jobs N
Number of parallel jobs to run. May also be specified with the

24
src/doc/man/generated_txt/cargo-remove.txt
View File

@ -61,16 +61,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -87,6 +90,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Package Selection
-p spec…, --package spec…
Package to remove from.

24
src/doc/man/generated_txt/cargo-run.txt
View File

@ -176,16 +176,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -202,6 +205,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/generated_txt/cargo-rustc.txt
View File

@ -274,16 +274,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -300,6 +303,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/generated_txt/cargo-rustdoc.txt
View File

@ -244,16 +244,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -270,6 +273,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/generated_txt/cargo-test.txt
View File

@ -364,16 +364,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -390,6 +393,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/generated_txt/cargo-tree.txt
View File

@ -211,16 +211,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -237,6 +240,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Feature Selection
The feature flags allow you to control which features are enabled. When
no feature options are given, the default feature is activated for every

24
src/doc/man/generated_txt/cargo-update.txt
View File

@ -81,16 +81,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -107,6 +110,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/generated_txt/cargo-vendor.txt
View File

@ -53,16 +53,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -79,6 +82,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Display Options
-v, --verbose
Use verbose output. May be specified twice for “very verbose”

24
src/doc/man/generated_txt/cargo-verify-project.txt
View File

@ -49,16 +49,19 @@ OPTIONS
Path to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--frozen, --locked
Either of these flags requires that the Cargo.lock file be
up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is
out-of-date.
--locked
Ensures that Cargo uses the exact version of every dependency
captured in the existing Cargo.lock file. Cargo will exit with an
error when either of the following scenarios arises:
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.
o The lock file is missing.
o The dependency resolution has changed, often caused by modifying
dependencies in the Cargo.toml file.
It may be used in environments where you want to assert that the
Cargo.lock file is up-to-date for reproducibility reasons, such as
in a CI build.
--offline
Prevents Cargo from accessing the network for any reason. Without
@ -75,6 +78,9 @@ OPTIONS
May also be specified with the net.offline config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--frozen
Equivalent to specifying both --locked and --offline.
Common Options
+toolchain
If Cargo has been installed with rustup, and the first argument to

24
src/doc/man/includes/options-locked.md
View File

@ -1,12 +1,14 @@
{{#option "`--frozen`" "`--locked`"}}
Either of these flags requires that the `Cargo.lock` file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The `--frozen` flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.
{{#option "`--locked`"}}
Ensures that Cargo uses the exact version of every dependency captured in the
existing `Cargo.lock` file. Cargo will exit with an error when either of the
following scenarios arises:
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.
* The lock file is missing.
* The dependency resolution has changed, often caused by modifying dependencies
in the `Cargo.toml` file.
It may be used in environments where you want to assert that the `Cargo.lock`
file is up-to-date for reproducibility reasons, such as in a CI build.
{{/option}}
{{#option "`--offline`"}}
@ -24,4 +26,8 @@ offline.
{{/if}}
May also be specified with the `net.offline` [config value](../reference/config.html).
{{/option}}
{{/option}}
{{#option "`--frozen`"}}
Equivalent to specifying both `--locked` and `--offline`.
{{/option}}

22
src/doc/src/commands/cargo-add.md
View File

@ -191,15 +191,17 @@ terminal.</li>
<dd class="option-desc">Add dependencies to only the specified package.</dd>
<dt class="option-term" id="option-cargo-add---frozen"><a class="option-anchor" href="#option-cargo-add---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-add---locked"><a class="option-anchor" href="#option-cargo-add---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-add---offline"><a class="option-anchor" href="#option-cargo-add---offline"></a><code>--offline</code></dt>
@ -214,6 +216,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-add---frozen"><a class="option-anchor" href="#option-cargo-add---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

22
src/doc/src/commands/cargo-bench.md
View File

@ -377,15 +377,17 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-bench---frozen"><a class="option-anchor" href="#option-cargo-bench---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-bench---locked"><a class="option-anchor" href="#option-cargo-bench---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-bench---offline"><a class="option-anchor" href="#option-cargo-bench---offline"></a><code>--offline</code></dt>
@ -400,6 +402,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-bench---frozen"><a class="option-anchor" href="#option-cargo-bench---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

22
src/doc/src/commands/cargo-build.md
View File

@ -308,15 +308,17 @@ See <a href="https://github.com/rust-lang/cargo/issues/5579">https://github.com/
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-build---frozen"><a class="option-anchor" href="#option-cargo-build---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-build---locked"><a class="option-anchor" href="#option-cargo-build---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-build---offline"><a class="option-anchor" href="#option-cargo-build---offline"></a><code>--offline</code></dt>
@ -331,6 +333,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-build---frozen"><a class="option-anchor" href="#option-cargo-build---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

22
src/doc/src/commands/cargo-check.md
View File

@ -290,15 +290,17 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-check---frozen"><a class="option-anchor" href="#option-cargo-check---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-check---locked"><a class="option-anchor" href="#option-cargo-check---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-check---offline"><a class="option-anchor" href="#option-cargo-check---offline"></a><code>--offline</code></dt>
@ -313,6 +315,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-check---frozen"><a class="option-anchor" href="#option-cargo-check---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

22
src/doc/src/commands/cargo-clean.md
View File

@ -110,15 +110,17 @@ terminal.</li>
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-clean---frozen"><a class="option-anchor" href="#option-cargo-clean---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-clean---locked"><a class="option-anchor" href="#option-cargo-clean---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-clean---offline"><a class="option-anchor" href="#option-cargo-clean---offline"></a><code>--offline</code></dt>
@ -133,6 +135,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-clean---frozen"><a class="option-anchor" href="#option-cargo-clean---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

22
src/doc/src/commands/cargo-doc.md
View File

@ -265,15 +265,17 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-doc---frozen"><a class="option-anchor" href="#option-cargo-doc---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-doc---locked"><a class="option-anchor" href="#option-cargo-doc---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-doc---offline"><a class="option-anchor" href="#option-cargo-doc---offline"></a><code>--offline</code></dt>
@ -288,6 +290,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-doc---frozen"><a class="option-anchor" href="#option-cargo-doc---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

22
src/doc/src/commands/cargo-fetch.md
View File

@ -79,15 +79,17 @@ terminal.</li>
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-fetch---frozen"><a class="option-anchor" href="#option-cargo-fetch---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-fetch---locked"><a class="option-anchor" href="#option-cargo-fetch---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-fetch---offline"><a class="option-anchor" href="#option-cargo-fetch---offline"></a><code>--offline</code></dt>
@ -100,6 +102,10 @@ 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.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-fetch---frozen"><a class="option-anchor" href="#option-cargo-fetch---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

22
src/doc/src/commands/cargo-fix.md
View File

@ -370,15 +370,17 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-fix---frozen"><a class="option-anchor" href="#option-cargo-fix---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-fix---locked"><a class="option-anchor" href="#option-cargo-fix---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-fix---offline"><a class="option-anchor" href="#option-cargo-fix---offline"></a><code>--offline</code></dt>
@ -393,6 +395,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-fix---frozen"><a class="option-anchor" href="#option-cargo-fix---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

22
src/doc/src/commands/cargo-generate-lockfile.md
View File

@ -58,15 +58,17 @@ terminal.</li>
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-generate-lockfile---frozen"><a class="option-anchor" href="#option-cargo-generate-lockfile---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-generate-lockfile---locked"><a class="option-anchor" href="#option-cargo-generate-lockfile---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-generate-lockfile---offline"><a class="option-anchor" href="#option-cargo-generate-lockfile---offline"></a><code>--offline</code></dt>
@ -81,6 +83,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-generate-lockfile---frozen"><a class="option-anchor" href="#option-cargo-generate-lockfile---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

22
src/doc/src/commands/cargo-install.md
View File

@ -266,15 +266,17 @@ information about timing information.</li>
### Manifest Options
<dl>
<dt class="option-term" id="option-cargo-install---frozen"><a class="option-anchor" href="#option-cargo-install---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-install---locked"><a class="option-anchor" href="#option-cargo-install---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-install---offline"><a class="option-anchor" href="#option-cargo-install---offline"></a><code>--offline</code></dt>
@ -289,6 +291,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-install---frozen"><a class="option-anchor" href="#option-cargo-install---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Miscellaneous Options

22
src/doc/src/commands/cargo-metadata.md
View File

@ -428,15 +428,17 @@ terminal.</li>
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-metadata---frozen"><a class="option-anchor" href="#option-cargo-metadata---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-metadata---locked"><a class="option-anchor" href="#option-cargo-metadata---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-metadata---offline"><a class="option-anchor" href="#option-cargo-metadata---offline"></a><code>--offline</code></dt>
@ -451,6 +453,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-metadata---frozen"><a class="option-anchor" href="#option-cargo-metadata---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

22
src/doc/src/commands/cargo-package.md
View File

@ -182,15 +182,17 @@ be specified multiple times, which enables all specified features.</dd>
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-package---frozen"><a class="option-anchor" href="#option-cargo-package---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-package---locked"><a class="option-anchor" href="#option-cargo-package---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-package---offline"><a class="option-anchor" href="#option-cargo-package---offline"></a><code>--offline</code></dt>
@ -206,6 +208,10 @@ offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-package---frozen"><a class="option-anchor" href="#option-cargo-package---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Miscellaneous Options

22
src/doc/src/commands/cargo-pkgid.md
View File

@ -90,15 +90,17 @@ terminal.</li>
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-pkgid---frozen"><a class="option-anchor" href="#option-cargo-pkgid---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-pkgid---locked"><a class="option-anchor" href="#option-cargo-pkgid---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-pkgid---offline"><a class="option-anchor" href="#option-cargo-pkgid---offline"></a><code>--offline</code></dt>
@ -114,6 +116,10 @@ offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-pkgid---frozen"><a class="option-anchor" href="#option-cargo-pkgid---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

22
src/doc/src/commands/cargo-publish.md
View File

@ -151,15 +151,17 @@ be specified multiple times, which enables all specified features.</dd>
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-publish---frozen"><a class="option-anchor" href="#option-cargo-publish---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-publish---locked"><a class="option-anchor" href="#option-cargo-publish---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-publish---offline"><a class="option-anchor" href="#option-cargo-publish---offline"></a><code>--offline</code></dt>
@ -175,6 +177,10 @@ offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-publish---frozen"><a class="option-anchor" href="#option-cargo-publish---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Miscellaneous Options

22
src/doc/src/commands/cargo-remove.md
View File

@ -81,15 +81,17 @@ terminal.</li>
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-remove---frozen"><a class="option-anchor" href="#option-cargo-remove---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-remove---locked"><a class="option-anchor" href="#option-cargo-remove---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-remove---offline"><a class="option-anchor" href="#option-cargo-remove---offline"></a><code>--offline</code></dt>
@ -104,6 +106,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-remove---frozen"><a class="option-anchor" href="#option-cargo-remove---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Package Selection

22
src/doc/src/commands/cargo-run.md
View File

@ -210,15 +210,17 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-run---frozen"><a class="option-anchor" href="#option-cargo-run---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-run---locked"><a class="option-anchor" href="#option-cargo-run---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-run---offline"><a class="option-anchor" href="#option-cargo-run---offline"></a><code>--offline</code></dt>
@ -234,6 +236,10 @@ offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-run---frozen"><a class="option-anchor" href="#option-cargo-run---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

22
src/doc/src/commands/cargo-rustc.md
View File

@ -304,15 +304,17 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-rustc---frozen"><a class="option-anchor" href="#option-cargo-rustc---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-rustc---locked"><a class="option-anchor" href="#option-cargo-rustc---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-rustc---offline"><a class="option-anchor" href="#option-cargo-rustc---offline"></a><code>--offline</code></dt>
@ -328,6 +330,10 @@ offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-rustc---frozen"><a class="option-anchor" href="#option-cargo-rustc---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

22
src/doc/src/commands/cargo-rustdoc.md
View File

@ -285,15 +285,17 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-rustdoc---frozen"><a class="option-anchor" href="#option-cargo-rustdoc---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-rustdoc---locked"><a class="option-anchor" href="#option-cargo-rustdoc---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-rustdoc---offline"><a class="option-anchor" href="#option-cargo-rustdoc---offline"></a><code>--offline</code></dt>
@ -308,6 +310,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-rustdoc---frozen"><a class="option-anchor" href="#option-cargo-rustdoc---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

22
src/doc/src/commands/cargo-test.md
View File

@ -406,15 +406,17 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-test---frozen"><a class="option-anchor" href="#option-cargo-test---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-test---locked"><a class="option-anchor" href="#option-cargo-test---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-test---offline"><a class="option-anchor" href="#option-cargo-test---offline"></a><code>--offline</code></dt>
@ -430,6 +432,10 @@ offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-test---frozen"><a class="option-anchor" href="#option-cargo-test---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

22
src/doc/src/commands/cargo-tree.md
View File

@ -222,15 +222,17 @@ single quotes or double quotes around each pattern.</dd>
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-tree---frozen"><a class="option-anchor" href="#option-cargo-tree---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-tree---locked"><a class="option-anchor" href="#option-cargo-tree---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-tree---offline"><a class="option-anchor" href="#option-cargo-tree---offline"></a><code>--offline</code></dt>
@ -246,6 +248,10 @@ offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-tree---frozen"><a class="option-anchor" href="#option-cargo-tree---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Feature Selection

22
src/doc/src/commands/cargo-update.md
View File

@ -99,15 +99,17 @@ terminal.</li>
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-update---frozen"><a class="option-anchor" href="#option-cargo-update---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-update---locked"><a class="option-anchor" href="#option-cargo-update---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-update---offline"><a class="option-anchor" href="#option-cargo-update---offline"></a><code>--offline</code></dt>
@ -123,6 +125,10 @@ offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-update---frozen"><a class="option-anchor" href="#option-cargo-update---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

22
src/doc/src/commands/cargo-vendor.md
View File

@ -68,15 +68,17 @@ only a subset of the packages have changed.</dd>
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-vendor---frozen"><a class="option-anchor" href="#option-cargo-vendor---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-vendor---locked"><a class="option-anchor" href="#option-cargo-vendor---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-vendor---offline"><a class="option-anchor" href="#option-cargo-vendor---offline"></a><code>--offline</code></dt>
@ -92,6 +94,10 @@ offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-vendor---frozen"><a class="option-anchor" href="#option-cargo-vendor---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Display Options

22
src/doc/src/commands/cargo-verify-project.md
View File

@ -63,15 +63,17 @@ terminal.</li>
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
<dt class="option-term" id="option-cargo-verify-project---frozen"><a class="option-anchor" href="#option-cargo-verify-project---frozen"></a><code>--frozen</code></dt>
<dt class="option-term" id="option-cargo-verify-project---locked"><a class="option-anchor" href="#option-cargo-verify-project---locked"></a><code>--locked</code></dt>
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
attempting to access the network to determine if it is out-of-date.</p>
<p>These may be used in environments where you want to assert that the
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
access.</dd>
<dd class="option-desc">Ensures that Cargo uses the exact version of every dependency captured in the
existing <code>Cargo.lock</code> file. Cargo will exit with an error when either of the
following scenarios arises:</p>
<ul>
<li>The lock file is missing.</li>
<li>The dependency resolution has changed, often caused by modifying dependencies
in the <code>Cargo.toml</code> file.</li>
</ul>
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
file is up-to-date for reproducibility reasons, such as in a CI build.</dd>
<dt class="option-term" id="option-cargo-verify-project---offline"><a class="option-anchor" href="#option-cargo-verify-project---offline"></a><code>--offline</code></dt>
@ -87,6 +89,10 @@ offline.</p>
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
<dt class="option-term" id="option-cargo-verify-project---frozen"><a class="option-anchor" href="#option-cargo-verify-project---frozen"></a><code>--frozen</code></dt>
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
</dl>
### Common Options

27
src/etc/man/cargo-add.1
View File

@ -221,17 +221,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
Add dependencies to only the specified package.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -249,6 +255,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

27
src/etc/man/cargo-bench.1
View File

@ -417,17 +417,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -445,6 +451,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

27
src/etc/man/cargo-build.1
View File

@ -335,17 +335,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -363,6 +369,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

27
src/etc/man/cargo-check.1
View File

@ -316,17 +316,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -344,6 +350,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

27
src/etc/man/cargo-clean.1
View File

@ -115,17 +115,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -143,6 +149,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

27
src/etc/man/cargo-doc.1
View File

@ -283,17 +283,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -311,6 +317,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

27
src/etc/man/cargo-fetch.1
View File

@ -83,17 +83,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -109,6 +115,11 @@ if there might be a newer version as indicated in the local copy of the index.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

27
src/etc/man/cargo-fix.1
View File

@ -411,17 +411,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -439,6 +445,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

27
src/etc/man/cargo-generate-lockfile.1
View File

@ -62,17 +62,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -90,6 +96,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

27
src/etc/man/cargo-install.1
View File

@ -302,17 +302,23 @@ information about timing information.
.RE
.SS "Manifest Options"
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -330,6 +336,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Miscellaneous Options"
.sp
\fB\-j\fR \fIN\fR,

27
src/etc/man/cargo-metadata.1
View File

@ -436,17 +436,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -464,6 +470,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

27
src/etc/man/cargo-package.1
View File

@ -198,17 +198,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -226,6 +232,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Miscellaneous Options"
.sp
\fB\-j\fR \fIN\fR,

27
src/etc/man/cargo-pkgid.1
View File

@ -121,17 +121,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -149,6 +155,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

27
src/etc/man/cargo-publish.1
View File

@ -154,17 +154,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -182,6 +188,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Miscellaneous Options"
.sp
\fB\-j\fR \fIN\fR,

27
src/etc/man/cargo-remove.1
View File

@ -81,17 +81,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -109,6 +115,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Package Selection"
.sp
\fB\-p\fR \fIspec\fR\[u2026],

27
src/etc/man/cargo-run.1
View File

@ -220,17 +220,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -248,6 +254,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

27
src/etc/man/cargo-rustc.1
View File

@ -334,17 +334,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -362,6 +368,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

27
src/etc/man/cargo-rustdoc.1
View File

@ -302,17 +302,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -330,6 +336,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

27
src/etc/man/cargo-test.1
View File

@ -444,17 +444,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -472,6 +478,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

27
src/etc/man/cargo-tree.1
View File

@ -266,17 +266,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -294,6 +300,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Feature Selection"
The feature flags allow you to control which features are enabled. When no
feature options are given, the \fBdefault\fR feature is activated for every

27
src/etc/man/cargo-update.1
View File

@ -105,17 +105,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -133,6 +139,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

27
src/etc/man/cargo-vendor.1
View File

@ -62,17 +62,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -90,6 +96,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Display Options"
.sp
\fB\-v\fR,

27
src/etc/man/cargo-verify-project.1
View File

@ -72,17 +72,23 @@ Path to the \fBCargo.toml\fR file. By default, Cargo searches for the
\fBCargo.toml\fR file in the current directory or any parent directory.
.RE
.sp
\fB\-\-frozen\fR,
\fB\-\-locked\fR
.RS 4
Either of these flags requires that the \fBCargo.lock\fR file be
up\-to\-date. If the lock file is missing, or it needs to be updated, Cargo will
exit with an error. The \fB\-\-frozen\fR flag also prevents Cargo from
attempting to access the network to determine if it is out\-of\-date.
Ensures that Cargo uses the exact version of every dependency captured in the
existing \fBCargo.lock\fR file. Cargo will exit with an error when either of the
following scenarios arises:
.sp
These may be used in environments where you want to assert that the
\fBCargo.lock\fR file is up\-to\-date (such as a CI build) or want to avoid network
access.
.RS 4
\h'-04'\(bu\h'+02'The lock file is missing.
.RE
.sp
.RS 4
\h'-04'\(bu\h'+02'The dependency resolution has changed, often caused by modifying dependencies
in the \fBCargo.toml\fR file.
.RE
.sp
It may be used in environments where you want to assert that the \fBCargo.lock\fR
file is up\-to\-date for reproducibility reasons, such as in a CI build.
.RE
.sp
\fB\-\-offline\fR
@ -100,6 +106,11 @@ offline.
.sp
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
.RE
.sp
\fB\-\-frozen\fR
.RS 4
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
.RE
.SS "Common Options"
.sp
\fB+\fR\fItoolchain\fR

6
tests/testsuite/cargo/help/stdout.term.svg
View File

@ -45,11 +45,11 @@
</tspan>
<tspan x="10px" y="244px"><tspan> </tspan><tspan class="fg-cyan bold">-C</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;DIRECTORY&gt;</tspan><tspan> Change to DIRECTORY before doing anything (nightly-only)</tspan>
</tspan>
<tspan x="10px" y="262px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="262px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="280px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="280px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="298px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="298px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--config</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;KEY=VALUE&gt;</tspan><tspan> Override a configuration value</tspan>
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 8.0 KiB

After

Width:  |  Height:  |  Size: 8.0 KiB

12
tests/testsuite/cargo_add/help/stdout.term.svg
View File

@ -179,21 +179,21 @@
</tspan>
<tspan x="10px" y="1450px">
</tspan>
<tspan x="10px" y="1468px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan>
<tspan x="10px" y="1468px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan>
</tspan>
<tspan x="10px" y="1486px"><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="1486px"><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="1504px">
</tspan>
<tspan x="10px" y="1522px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan>
<tspan x="10px" y="1522px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan>
</tspan>
<tspan x="10px" y="1540px"><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="1540px"><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="1558px">
</tspan>
<tspan x="10px" y="1576px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan>
<tspan x="10px" y="1576px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan>
</tspan>
<tspan x="10px" y="1594px"><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="1594px"><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="1612px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 14 KiB

After

Width:  |  Height:  |  Size: 14 KiB

6
tests/testsuite/cargo_bench/help/stdout.term.svg
View File

@ -127,11 +127,11 @@
</tspan>
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="1018px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="1018px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="1036px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="1036px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="1054px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 10 KiB

After

Width:  |  Height:  |  Size: 10 KiB

6
tests/testsuite/cargo_build/help/stdout.term.svg
View File

@ -125,11 +125,11 @@
</tspan>
<tspan x="10px" y="964px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="1018px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="1018px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="1036px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 10 KiB

After

Width:  |  Height:  |  Size: 11 KiB

6
tests/testsuite/cargo_check/help/stdout.term.svg
View File

@ -121,11 +121,11 @@
</tspan>
<tspan x="10px" y="928px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="946px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="946px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="964px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="964px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="1000px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 10 KiB

After

Width:  |  Height:  |  Size: 10 KiB

6
tests/testsuite/cargo_clean/help/stdout.term.svg
View File

@ -69,11 +69,11 @@
</tspan>
<tspan x="10px" y="460px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="532px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 5.5 KiB

After

Width:  |  Height:  |  Size: 5.5 KiB

6
tests/testsuite/cargo_config/help/stdout.term.svg
View File

@ -51,11 +51,11 @@
</tspan>
<tspan x="10px" y="298px"><tspan class="fg-green bold">Manifest Options:</tspan>
</tspan>
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="370px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 3.3 KiB

After

Width:  |  Height:  |  Size: 3.4 KiB

6
tests/testsuite/cargo_doc/help/stdout.term.svg
View File

@ -115,11 +115,11 @@
</tspan>
<tspan x="10px" y="874px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="892px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="892px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="910px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="910px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="928px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="928px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="946px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 9.4 KiB

After

Width:  |  Height:  |  Size: 9.5 KiB

6
tests/testsuite/cargo_fetch/help/stdout.term.svg
View File

@ -53,11 +53,11 @@
</tspan>
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="370px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="370px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="388px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 3.9 KiB

After

Width:  |  Height:  |  Size: 4.0 KiB

6
tests/testsuite/cargo_fix/help/stdout.term.svg
View File

@ -129,11 +129,11 @@
</tspan>
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="1018px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="1018px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="1036px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="1036px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="1054px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="1054px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="1072px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 11 KiB

After

Width:  |  Height:  |  Size: 11 KiB

6
tests/testsuite/cargo_generate_lockfile/help/stdout.term.svg
View File

@ -47,11 +47,11 @@
</tspan>
<tspan x="10px" y="262px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="280px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="280px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="298px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="298px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="334px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 3.5 KiB

After

Width:  |  Height:  |  Size: 3.6 KiB

6
tests/testsuite/cargo_help/help/stdout.term.svg
View File

@ -51,11 +51,11 @@
</tspan>
<tspan x="10px" y="298px"><tspan class="fg-green bold">Manifest Options:</tspan>
</tspan>
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="370px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 3.3 KiB

After

Width:  |  Height:  |  Size: 3.4 KiB

6
tests/testsuite/cargo_init/help/stdout.term.svg
View File

@ -69,11 +69,11 @@
</tspan>
<tspan x="10px" y="460px"><tspan class="fg-green bold">Manifest Options:</tspan>
</tspan>
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="532px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 5.2 KiB

After

Width:  |  Height:  |  Size: 5.3 KiB

6
tests/testsuite/cargo_install/help/stdout.term.svg
View File

@ -121,11 +121,11 @@
</tspan>
<tspan x="10px" y="928px"><tspan class="fg-green bold">Manifest Options:</tspan>
</tspan>
<tspan x="10px" y="946px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="946px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="964px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="964px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="1000px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 10 KiB

After

Width:  |  Height:  |  Size: 10 KiB

6
tests/testsuite/cargo_locate_project/help/stdout.term.svg
View File

@ -53,11 +53,11 @@
</tspan>
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="370px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="370px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="388px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 4.1 KiB

After

Width:  |  Height:  |  Size: 4.1 KiB

6
tests/testsuite/cargo_login/help/stdout.term.svg
View File

@ -55,11 +55,11 @@
</tspan>
<tspan x="10px" y="334px"><tspan class="fg-green bold">Manifest Options:</tspan>
</tspan>
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="370px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="370px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="388px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="388px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="406px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 4.1 KiB

After

Width:  |  Height:  |  Size: 4.1 KiB

6
tests/testsuite/cargo_logout/help/stdout.term.svg
View File

@ -47,11 +47,11 @@
</tspan>
<tspan x="10px" y="262px"><tspan class="fg-green bold">Manifest Options:</tspan>
</tspan>
<tspan x="10px" y="280px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="280px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="298px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="298px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="334px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 3.5 KiB

After

Width:  |  Height:  |  Size: 3.5 KiB

6
tests/testsuite/cargo_metadata/help/stdout.term.svg
View File

@ -69,11 +69,11 @@
</tspan>
<tspan x="10px" y="460px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="532px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 5.3 KiB

After

Width:  |  Height:  |  Size: 5.4 KiB

6
tests/testsuite/cargo_new/help/stdout.term.svg
View File

@ -69,11 +69,11 @@
</tspan>
<tspan x="10px" y="460px"><tspan class="fg-green bold">Manifest Options:</tspan>
</tspan>
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="532px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 5.2 KiB

After

Width:  |  Height:  |  Size: 5.3 KiB

6
tests/testsuite/cargo_owner/help/stdout.term.svg
View File

@ -63,11 +63,11 @@
</tspan>
<tspan x="10px" y="406px"><tspan class="fg-green bold">Manifest Options:</tspan>
</tspan>
<tspan x="10px" y="424px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="424px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="442px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="442px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="460px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="460px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="478px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 5.0 KiB

After

Width:  |  Height:  |  Size: 5.1 KiB

6
tests/testsuite/cargo_package/help/stdout.term.svg
View File

@ -87,11 +87,11 @@
</tspan>
<tspan x="10px" y="622px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="640px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="640px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="658px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="658px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="676px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="676px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="694px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 7.0 KiB

After

Width:  |  Height:  |  Size: 7.0 KiB

6
tests/testsuite/cargo_pkgid/help/stdout.term.svg
View File

@ -59,11 +59,11 @@
</tspan>
<tspan x="10px" y="370px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="388px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="388px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="406px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="406px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="424px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="424px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="442px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 4.3 KiB

After

Width:  |  Height:  |  Size: 4.3 KiB

6
tests/testsuite/cargo_publish/help/stdout.term.svg
View File

@ -87,11 +87,11 @@
</tspan>
<tspan x="10px" y="622px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="640px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="640px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="658px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="658px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="676px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="676px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="694px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 7.1 KiB

After

Width:  |  Height:  |  Size: 7.1 KiB

6
tests/testsuite/cargo_read_manifest/help/stdout.term.svg
View File

@ -51,11 +51,11 @@
</tspan>
<tspan x="10px" y="298px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="370px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 3.5 KiB

After

Width:  |  Height:  |  Size: 3.6 KiB

6
tests/testsuite/cargo_remove/help/stdout.term.svg
View File

@ -71,11 +71,11 @@
</tspan>
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="532px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="532px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="550px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 5.2 KiB

After

Width:  |  Height:  |  Size: 5.2 KiB

6
tests/testsuite/cargo_report/help/stdout.term.svg
View File

@ -51,11 +51,11 @@
</tspan>
<tspan x="10px" y="298px"><tspan class="fg-green bold">Manifest Options:</tspan>
</tspan>
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="370px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 3.6 KiB

After

Width:  |  Height:  |  Size: 3.7 KiB

6
tests/testsuite/cargo_run/help/stdout.term.svg
View File

@ -103,11 +103,11 @@
</tspan>
<tspan x="10px" y="766px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="784px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="784px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="802px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="802px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="820px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="820px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="838px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 8.2 KiB

After

Width:  |  Height:  |  Size: 8.3 KiB

6
tests/testsuite/cargo_rustc/help/stdout.term.svg
View File

@ -125,11 +125,11 @@
</tspan>
<tspan x="10px" y="964px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="1018px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="1018px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="1036px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 10 KiB

After

Width:  |  Height:  |  Size: 10 KiB

6
tests/testsuite/cargo_rustdoc/help/stdout.term.svg
View File

@ -123,11 +123,11 @@
</tspan>
<tspan x="10px" y="946px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan">&lt;PATH&gt;</tspan><tspan> Path to Cargo.toml</tspan>
</tspan>
<tspan x="10px" y="964px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
<tspan x="10px" y="964px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Ensure the exact dependency versions in Cargo.lock is used</tspan>
</tspan>
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
</tspan>
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
</tspan>
<tspan x="10px" y="1018px">
</tspan>

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 10 KiB

After

Width:  |  Height:  |  Size: 10 KiB

Some files were not shown because too many files have changed in this diff Show More