diff --git a/src/bin/cargo/cli.rs b/src/bin/cargo/cli.rs index 40a8ae706..c2b7991d9 100644 --- a/src/bin/cargo/cli.rs +++ b/src/bin/cargo/cli.rs @@ -640,12 +640,7 @@ See 'cargo help <>' 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 'cargo help <>' 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("") diff --git a/src/doc/man/generated_txt/cargo-add.txt b/src/doc/man/generated_txt/cargo-add.txt index a7246e38a..b10ba52b6 100644 --- a/src/doc/man/generated_txt/cargo-add.txt +++ b/src/doc/man/generated_txt/cargo-add.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/generated_txt/cargo-bench.txt b/src/doc/man/generated_txt/cargo-bench.txt index 03448ee50..484c47770 100644 --- a/src/doc/man/generated_txt/cargo-bench.txt +++ b/src/doc/man/generated_txt/cargo-bench.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/generated_txt/cargo-build.txt b/src/doc/man/generated_txt/cargo-build.txt index dd404a3ed..0aa8760ff 100644 --- a/src/doc/man/generated_txt/cargo-build.txt +++ b/src/doc/man/generated_txt/cargo-build.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/generated_txt/cargo-check.txt b/src/doc/man/generated_txt/cargo-check.txt index 6135fdc21..33095a532 100644 --- a/src/doc/man/generated_txt/cargo-check.txt +++ b/src/doc/man/generated_txt/cargo-check.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/generated_txt/cargo-clean.txt b/src/doc/man/generated_txt/cargo-clean.txt index 38e48cb52..f106093b5 100644 --- a/src/doc/man/generated_txt/cargo-clean.txt +++ b/src/doc/man/generated_txt/cargo-clean.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/generated_txt/cargo-doc.txt b/src/doc/man/generated_txt/cargo-doc.txt index d5e6ddf49..ed0c3d525 100644 --- a/src/doc/man/generated_txt/cargo-doc.txt +++ b/src/doc/man/generated_txt/cargo-doc.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/generated_txt/cargo-fetch.txt b/src/doc/man/generated_txt/cargo-fetch.txt index bf9c3c215..c45b4bea7 100644 --- a/src/doc/man/generated_txt/cargo-fetch.txt +++ b/src/doc/man/generated_txt/cargo-fetch.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/generated_txt/cargo-fix.txt b/src/doc/man/generated_txt/cargo-fix.txt index 25014ab08..28c6e9fe9 100644 --- a/src/doc/man/generated_txt/cargo-fix.txt +++ b/src/doc/man/generated_txt/cargo-fix.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/generated_txt/cargo-generate-lockfile.txt b/src/doc/man/generated_txt/cargo-generate-lockfile.txt index 9ec3af709..3b95bc86f 100644 --- a/src/doc/man/generated_txt/cargo-generate-lockfile.txt +++ b/src/doc/man/generated_txt/cargo-generate-lockfile.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/generated_txt/cargo-install.txt b/src/doc/man/generated_txt/cargo-install.txt index e9cd80b42..ff4427bf9 100644 --- a/src/doc/man/generated_txt/cargo-install.txt +++ b/src/doc/man/generated_txt/cargo-install.txt @@ -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 . + --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 diff --git a/src/doc/man/generated_txt/cargo-metadata.txt b/src/doc/man/generated_txt/cargo-metadata.txt index 7643a021d..ba29f62af 100644 --- a/src/doc/man/generated_txt/cargo-metadata.txt +++ b/src/doc/man/generated_txt/cargo-metadata.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/generated_txt/cargo-package.txt b/src/doc/man/generated_txt/cargo-package.txt index 1cdf31f49..970314157 100644 --- a/src/doc/man/generated_txt/cargo-package.txt +++ b/src/doc/man/generated_txt/cargo-package.txt @@ -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 . + --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 diff --git a/src/doc/man/generated_txt/cargo-pkgid.txt b/src/doc/man/generated_txt/cargo-pkgid.txt index e1c889b37..4859955ae 100644 --- a/src/doc/man/generated_txt/cargo-pkgid.txt +++ b/src/doc/man/generated_txt/cargo-pkgid.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/generated_txt/cargo-publish.txt b/src/doc/man/generated_txt/cargo-publish.txt index fbffc706c..66b6a72d5 100644 --- a/src/doc/man/generated_txt/cargo-publish.txt +++ b/src/doc/man/generated_txt/cargo-publish.txt @@ -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 . + --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 diff --git a/src/doc/man/generated_txt/cargo-remove.txt b/src/doc/man/generated_txt/cargo-remove.txt index 21a0ec275..37dbf8f9f 100644 --- a/src/doc/man/generated_txt/cargo-remove.txt +++ b/src/doc/man/generated_txt/cargo-remove.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Package Selection -p spec…, --package spec… Package to remove from. diff --git a/src/doc/man/generated_txt/cargo-run.txt b/src/doc/man/generated_txt/cargo-run.txt index dc9b28229..16dcd1504 100644 --- a/src/doc/man/generated_txt/cargo-run.txt +++ b/src/doc/man/generated_txt/cargo-run.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/generated_txt/cargo-rustc.txt b/src/doc/man/generated_txt/cargo-rustc.txt index 4e0abc0fd..acf7d084a 100644 --- a/src/doc/man/generated_txt/cargo-rustc.txt +++ b/src/doc/man/generated_txt/cargo-rustc.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/generated_txt/cargo-rustdoc.txt b/src/doc/man/generated_txt/cargo-rustdoc.txt index 3319eb838..8a322509b 100644 --- a/src/doc/man/generated_txt/cargo-rustdoc.txt +++ b/src/doc/man/generated_txt/cargo-rustdoc.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/generated_txt/cargo-test.txt b/src/doc/man/generated_txt/cargo-test.txt index f9d1cb343..72c834403 100644 --- a/src/doc/man/generated_txt/cargo-test.txt +++ b/src/doc/man/generated_txt/cargo-test.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/generated_txt/cargo-tree.txt b/src/doc/man/generated_txt/cargo-tree.txt index 57e74b118..579305641 100644 --- a/src/doc/man/generated_txt/cargo-tree.txt +++ b/src/doc/man/generated_txt/cargo-tree.txt @@ -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 . + --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 diff --git a/src/doc/man/generated_txt/cargo-update.txt b/src/doc/man/generated_txt/cargo-update.txt index 0f00fa043..17c0aeed9 100644 --- a/src/doc/man/generated_txt/cargo-update.txt +++ b/src/doc/man/generated_txt/cargo-update.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/generated_txt/cargo-vendor.txt b/src/doc/man/generated_txt/cargo-vendor.txt index 190497132..94a66f918 100644 --- a/src/doc/man/generated_txt/cargo-vendor.txt +++ b/src/doc/man/generated_txt/cargo-vendor.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Display Options -v, --verbose Use verbose output. May be specified twice for “very verbose” diff --git a/src/doc/man/generated_txt/cargo-verify-project.txt b/src/doc/man/generated_txt/cargo-verify-project.txt index c790d23aa..b35c96c13 100644 --- a/src/doc/man/generated_txt/cargo-verify-project.txt +++ b/src/doc/man/generated_txt/cargo-verify-project.txt @@ -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 . + --frozen + Equivalent to specifying both --locked and --offline. + Common Options +toolchain If Cargo has been installed with rustup, and the first argument to diff --git a/src/doc/man/includes/options-locked.md b/src/doc/man/includes/options-locked.md index deb86bce0..b080da06d 100644 --- a/src/doc/man/includes/options-locked.md +++ b/src/doc/man/includes/options-locked.md @@ -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}} \ No newline at end of file +{{/option}} + +{{#option "`--frozen`"}} +Equivalent to specifying both `--locked` and `--offline`. +{{/option}} diff --git a/src/doc/src/commands/cargo-add.md b/src/doc/src/commands/cargo-add.md index 9f599d37c..400734169 100644 --- a/src/doc/src/commands/cargo-add.md +++ b/src/doc/src/commands/cargo-add.md @@ -191,15 +191,17 @@ terminal.
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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -214,6 +216,10 @@ See the cargo-fetch(1) command to download depend offline.

May also be specified with the net.offline config value. + +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ ### Common Options diff --git a/src/doc/src/commands/cargo-bench.md b/src/doc/src/commands/cargo-bench.md index 8b26e76f1..9f31b1c39 100644 --- a/src/doc/src/commands/cargo-bench.md +++ b/src/doc/src/commands/cargo-bench.md @@ -377,15 +377,17 @@ coming from rustc are still emitted. Cannot be used with human or < 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -400,6 +402,10 @@ See the cargo-fetch(1) command to download depend offline.

May also be specified with the net.offline config value. + +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ ### Common Options diff --git a/src/doc/src/commands/cargo-build.md b/src/doc/src/commands/cargo-build.md index fb91f7d2d..a81b36119 100644 --- a/src/doc/src/commands/cargo-build.md +++ b/src/doc/src/commands/cargo-build.md @@ -308,15 +308,17 @@ See https://github.com/ 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -331,6 +333,10 @@ See the cargo-fetch(1) command to download depend offline.

May also be specified with the net.offline config value. + +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ ### Common Options diff --git a/src/doc/src/commands/cargo-check.md b/src/doc/src/commands/cargo-check.md index f011e5539..bac4bd3e8 100644 --- a/src/doc/src/commands/cargo-check.md +++ b/src/doc/src/commands/cargo-check.md @@ -290,15 +290,17 @@ coming from rustc are still emitted. Cannot be used with human or < 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -313,6 +315,10 @@ See the cargo-fetch(1) command to download depend offline.

May also be specified with the net.offline config value. + +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ ### Common Options diff --git a/src/doc/src/commands/cargo-clean.md b/src/doc/src/commands/cargo-clean.md index dc9f05e8b..bcadfbb53 100644 --- a/src/doc/src/commands/cargo-clean.md +++ b/src/doc/src/commands/cargo-clean.md @@ -110,15 +110,17 @@ terminal. 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -133,6 +135,10 @@ See the cargo-fetch(1) command to download depend offline.

May also be specified with the net.offline config value. + +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ ### Common Options diff --git a/src/doc/src/commands/cargo-doc.md b/src/doc/src/commands/cargo-doc.md index da56c768c..81e6ee060 100644 --- a/src/doc/src/commands/cargo-doc.md +++ b/src/doc/src/commands/cargo-doc.md @@ -265,15 +265,17 @@ coming from rustc are still emitted. Cannot be used with human or < 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -288,6 +290,10 @@ See the cargo-fetch(1) command to download depend offline.

May also be specified with the net.offline config value. + +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ ### Common Options diff --git a/src/doc/src/commands/cargo-fetch.md b/src/doc/src/commands/cargo-fetch.md index 04e2de50e..f48ec3be2 100644 --- a/src/doc/src/commands/cargo-fetch.md +++ b/src/doc/src/commands/cargo-fetch.md @@ -79,15 +79,17 @@ terminal. 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -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.

May also be specified with the net.offline config value. + +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ ### Common Options diff --git a/src/doc/src/commands/cargo-fix.md b/src/doc/src/commands/cargo-fix.md index 5dcc36f07..58c73a39a 100644 --- a/src/doc/src/commands/cargo-fix.md +++ b/src/doc/src/commands/cargo-fix.md @@ -370,15 +370,17 @@ coming from rustc are still emitted. Cannot be used with human or < 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -393,6 +395,10 @@ See the cargo-fetch(1) command to download depend offline.

May also be specified with the net.offline config value. + +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ ### Common Options diff --git a/src/doc/src/commands/cargo-generate-lockfile.md b/src/doc/src/commands/cargo-generate-lockfile.md index dfa4c6996..54ff6ddaa 100644 --- a/src/doc/src/commands/cargo-generate-lockfile.md +++ b/src/doc/src/commands/cargo-generate-lockfile.md @@ -58,15 +58,17 @@ terminal. 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -81,6 +83,10 @@ See the cargo-fetch(1) command to download depend offline.

May also be specified with the net.offline config value. + +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ ### Common Options diff --git a/src/doc/src/commands/cargo-install.md b/src/doc/src/commands/cargo-install.md index 423b9f117..333add2c8 100644 --- a/src/doc/src/commands/cargo-install.md +++ b/src/doc/src/commands/cargo-install.md @@ -266,15 +266,17 @@ 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -289,6 +291,10 @@ See the cargo-fetch(1) command to download depend offline.

May also be specified with the net.offline config value. + +

--frozen
+
Equivalent to specifying both --locked and --offline.
+
### Miscellaneous Options diff --git a/src/doc/src/commands/cargo-metadata.md b/src/doc/src/commands/cargo-metadata.md index 7cbf03daf..0a9bb0aff 100644 --- a/src/doc/src/commands/cargo-metadata.md +++ b/src/doc/src/commands/cargo-metadata.md @@ -428,15 +428,17 @@ terminal. 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -451,6 +453,10 @@ See the cargo-fetch(1) command to download depend offline.

May also be specified with the net.offline config value. + +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ ### Common Options diff --git a/src/doc/src/commands/cargo-package.md b/src/doc/src/commands/cargo-package.md index 2158d202f..55ef5c772 100644 --- a/src/doc/src/commands/cargo-package.md +++ b/src/doc/src/commands/cargo-package.md @@ -182,15 +182,17 @@ be specified multiple times, which enables all specified features. 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -206,6 +208,10 @@ offline.

May also be specified with the net.offline config value. +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ + ### Miscellaneous Options diff --git a/src/doc/src/commands/cargo-pkgid.md b/src/doc/src/commands/cargo-pkgid.md index 523cc3c6e..f20531609 100644 --- a/src/doc/src/commands/cargo-pkgid.md +++ b/src/doc/src/commands/cargo-pkgid.md @@ -90,15 +90,17 @@ terminal. 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -114,6 +116,10 @@ offline.

May also be specified with the net.offline config value. +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ + ### Common Options diff --git a/src/doc/src/commands/cargo-publish.md b/src/doc/src/commands/cargo-publish.md index d0bbbc074..f01134bce 100644 --- a/src/doc/src/commands/cargo-publish.md +++ b/src/doc/src/commands/cargo-publish.md @@ -151,15 +151,17 @@ be specified multiple times, which enables all specified features. 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -175,6 +177,10 @@ offline.

May also be specified with the net.offline config value. +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ + ### Miscellaneous Options diff --git a/src/doc/src/commands/cargo-remove.md b/src/doc/src/commands/cargo-remove.md index a59e0232e..df615a71c 100644 --- a/src/doc/src/commands/cargo-remove.md +++ b/src/doc/src/commands/cargo-remove.md @@ -81,15 +81,17 @@ terminal. 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -104,6 +106,10 @@ See the cargo-fetch(1) command to download depend offline.

May also be specified with the net.offline config value. + +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ ### Package Selection diff --git a/src/doc/src/commands/cargo-run.md b/src/doc/src/commands/cargo-run.md index b79913194..01451a857 100644 --- a/src/doc/src/commands/cargo-run.md +++ b/src/doc/src/commands/cargo-run.md @@ -210,15 +210,17 @@ coming from rustc are still emitted. Cannot be used with human or < 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -234,6 +236,10 @@ offline.

May also be specified with the net.offline config value. +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ + ### Common Options diff --git a/src/doc/src/commands/cargo-rustc.md b/src/doc/src/commands/cargo-rustc.md index 7ad9bff16..f170f30ef 100644 --- a/src/doc/src/commands/cargo-rustc.md +++ b/src/doc/src/commands/cargo-rustc.md @@ -304,15 +304,17 @@ coming from rustc are still emitted. Cannot be used with human or < 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -328,6 +330,10 @@ offline.

May also be specified with the net.offline config value. +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ + ### Common Options diff --git a/src/doc/src/commands/cargo-rustdoc.md b/src/doc/src/commands/cargo-rustdoc.md index 0ebb62efb..d33414f6e 100644 --- a/src/doc/src/commands/cargo-rustdoc.md +++ b/src/doc/src/commands/cargo-rustdoc.md @@ -285,15 +285,17 @@ coming from rustc are still emitted. Cannot be used with human or < 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -308,6 +310,10 @@ See the cargo-fetch(1) command to download depend offline.

May also be specified with the net.offline config value. + +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ ### Common Options diff --git a/src/doc/src/commands/cargo-test.md b/src/doc/src/commands/cargo-test.md index 127311cc5..9deae96d4 100644 --- a/src/doc/src/commands/cargo-test.md +++ b/src/doc/src/commands/cargo-test.md @@ -406,15 +406,17 @@ coming from rustc are still emitted. Cannot be used with human or < 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -430,6 +432,10 @@ offline.

May also be specified with the net.offline config value. +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ + ### Common Options diff --git a/src/doc/src/commands/cargo-tree.md b/src/doc/src/commands/cargo-tree.md index 5997c9d20..dd5f427dc 100644 --- a/src/doc/src/commands/cargo-tree.md +++ b/src/doc/src/commands/cargo-tree.md @@ -222,15 +222,17 @@ single quotes or double quotes around each pattern. 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -246,6 +248,10 @@ offline.

May also be specified with the net.offline config value. +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ + ### Feature Selection diff --git a/src/doc/src/commands/cargo-update.md b/src/doc/src/commands/cargo-update.md index f8d90903f..af645d565 100644 --- a/src/doc/src/commands/cargo-update.md +++ b/src/doc/src/commands/cargo-update.md @@ -99,15 +99,17 @@ terminal. 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -123,6 +125,10 @@ offline.

May also be specified with the net.offline config value. +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ + ### Common Options diff --git a/src/doc/src/commands/cargo-vendor.md b/src/doc/src/commands/cargo-vendor.md index 542333afb..6fc167cb6 100644 --- a/src/doc/src/commands/cargo-vendor.md +++ b/src/doc/src/commands/cargo-vendor.md @@ -68,15 +68,17 @@ only a subset of the packages have changed. 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -92,6 +94,10 @@ offline.

May also be specified with the net.offline config value. +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ + ### Display Options diff --git a/src/doc/src/commands/cargo-verify-project.md b/src/doc/src/commands/cargo-verify-project.md index a62ee2aaa..7347dac02 100644 --- a/src/doc/src/commands/cargo-verify-project.md +++ b/src/doc/src/commands/cargo-verify-project.md @@ -63,15 +63,17 @@ terminal. 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.

-

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.

+
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:

+
    +
  • 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.

--offline
@@ -87,6 +89,10 @@ offline.

May also be specified with the net.offline config value. +

--frozen
+
Equivalent to specifying both --locked and --offline.
+ + ### Common Options diff --git a/src/etc/man/cargo-add.1 b/src/etc/man/cargo-add.1 index c44a48346..b57c850da 100644 --- a/src/etc/man/cargo-add.1 +++ b/src/etc/man/cargo-add.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-bench.1 b/src/etc/man/cargo-bench.1 index 4f1ff291a..81f11428b 100644 --- a/src/etc/man/cargo-bench.1 +++ b/src/etc/man/cargo-bench.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-build.1 b/src/etc/man/cargo-build.1 index b0f04738a..140721eba 100644 --- a/src/etc/man/cargo-build.1 +++ b/src/etc/man/cargo-build.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-check.1 b/src/etc/man/cargo-check.1 index 2e2d8a6b0..c86dfa3e4 100644 --- a/src/etc/man/cargo-check.1 +++ b/src/etc/man/cargo-check.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-clean.1 b/src/etc/man/cargo-clean.1 index 621804d1b..7d8dc6904 100644 --- a/src/etc/man/cargo-clean.1 +++ b/src/etc/man/cargo-clean.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-doc.1 b/src/etc/man/cargo-doc.1 index 3832e7282..c10f716a3 100644 --- a/src/etc/man/cargo-doc.1 +++ b/src/etc/man/cargo-doc.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-fetch.1 b/src/etc/man/cargo-fetch.1 index b63b9090c..6819eafff 100644 --- a/src/etc/man/cargo-fetch.1 +++ b/src/etc/man/cargo-fetch.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-fix.1 b/src/etc/man/cargo-fix.1 index 22ac0b7ed..edfb9ca75 100644 --- a/src/etc/man/cargo-fix.1 +++ b/src/etc/man/cargo-fix.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-generate-lockfile.1 b/src/etc/man/cargo-generate-lockfile.1 index c98366c57..50e2cfbc2 100644 --- a/src/etc/man/cargo-generate-lockfile.1 +++ b/src/etc/man/cargo-generate-lockfile.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-install.1 b/src/etc/man/cargo-install.1 index 8ab35749a..6aa766f51 100644 --- a/src/etc/man/cargo-install.1 +++ b/src/etc/man/cargo-install.1 @@ -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 \&. .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, diff --git a/src/etc/man/cargo-metadata.1 b/src/etc/man/cargo-metadata.1 index a020153d2..04fec9c48 100644 --- a/src/etc/man/cargo-metadata.1 +++ b/src/etc/man/cargo-metadata.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-package.1 b/src/etc/man/cargo-package.1 index b88b7a6a4..2b385a22b 100644 --- a/src/etc/man/cargo-package.1 +++ b/src/etc/man/cargo-package.1 @@ -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 \&. .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, diff --git a/src/etc/man/cargo-pkgid.1 b/src/etc/man/cargo-pkgid.1 index bc5e99d4f..132361b88 100644 --- a/src/etc/man/cargo-pkgid.1 +++ b/src/etc/man/cargo-pkgid.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-publish.1 b/src/etc/man/cargo-publish.1 index bf4cea1c2..c8ec93af4 100644 --- a/src/etc/man/cargo-publish.1 +++ b/src/etc/man/cargo-publish.1 @@ -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 \&. .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, diff --git a/src/etc/man/cargo-remove.1 b/src/etc/man/cargo-remove.1 index 0c632083c..b3e5e4e07 100644 --- a/src/etc/man/cargo-remove.1 +++ b/src/etc/man/cargo-remove.1 @@ -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 \&. .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], diff --git a/src/etc/man/cargo-run.1 b/src/etc/man/cargo-run.1 index 58569d77e..23a9b4016 100644 --- a/src/etc/man/cargo-run.1 +++ b/src/etc/man/cargo-run.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-rustc.1 b/src/etc/man/cargo-rustc.1 index e5f963f79..cdf05d40d 100644 --- a/src/etc/man/cargo-rustc.1 +++ b/src/etc/man/cargo-rustc.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-rustdoc.1 b/src/etc/man/cargo-rustdoc.1 index 4e7216c67..6e3e0a410 100644 --- a/src/etc/man/cargo-rustdoc.1 +++ b/src/etc/man/cargo-rustdoc.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-test.1 b/src/etc/man/cargo-test.1 index d760c8556..df11712d6 100644 --- a/src/etc/man/cargo-test.1 +++ b/src/etc/man/cargo-test.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-tree.1 b/src/etc/man/cargo-tree.1 index 280aec235..b5705027e 100644 --- a/src/etc/man/cargo-tree.1 +++ b/src/etc/man/cargo-tree.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-update.1 b/src/etc/man/cargo-update.1 index ac1e5a7a1..993ba0a79 100644 --- a/src/etc/man/cargo-update.1 +++ b/src/etc/man/cargo-update.1 @@ -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 \&. .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 diff --git a/src/etc/man/cargo-vendor.1 b/src/etc/man/cargo-vendor.1 index 92bd9f34c..9bbe68937 100644 --- a/src/etc/man/cargo-vendor.1 +++ b/src/etc/man/cargo-vendor.1 @@ -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 \&. .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, diff --git a/src/etc/man/cargo-verify-project.1 b/src/etc/man/cargo-verify-project.1 index 1e36a66b6..cb53ef6c6 100644 --- a/src/etc/man/cargo-verify-project.1 +++ b/src/etc/man/cargo-verify-project.1 @@ -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 \&. .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 diff --git a/tests/testsuite/cargo/help/stdout.term.svg b/tests/testsuite/cargo/help/stdout.term.svg index e29e2acff..96b255166 100644 --- a/tests/testsuite/cargo/help/stdout.term.svg +++ b/tests/testsuite/cargo/help/stdout.term.svg @@ -45,11 +45,11 @@ -C <DIRECTORY> Change to DIRECTORY before doing anything (nightly-only) - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline --config <KEY=VALUE> Override a configuration value diff --git a/tests/testsuite/cargo_add/help/stdout.term.svg b/tests/testsuite/cargo_add/help/stdout.term.svg index b6a4a476e..1c67fab1c 100644 --- a/tests/testsuite/cargo_add/help/stdout.term.svg +++ b/tests/testsuite/cargo_add/help/stdout.term.svg @@ -179,21 +179,21 @@ - --frozen + --locked - Require Cargo.lock and cache to be up-to-date + Ensure the exact dependency versions in Cargo.lock is used - --locked + --offline - Require Cargo.lock to be up-to-date + Run without accessing the network - --offline + --frozen - Run without accessing the network + Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_bench/help/stdout.term.svg b/tests/testsuite/cargo_bench/help/stdout.term.svg index 1ea535a0b..ae5b430c4 100644 --- a/tests/testsuite/cargo_bench/help/stdout.term.svg +++ b/tests/testsuite/cargo_bench/help/stdout.term.svg @@ -127,11 +127,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_build/help/stdout.term.svg b/tests/testsuite/cargo_build/help/stdout.term.svg index 92095ae15..ae1a10909 100644 --- a/tests/testsuite/cargo_build/help/stdout.term.svg +++ b/tests/testsuite/cargo_build/help/stdout.term.svg @@ -125,11 +125,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_check/help/stdout.term.svg b/tests/testsuite/cargo_check/help/stdout.term.svg index 8ef0b9b32..76a225196 100644 --- a/tests/testsuite/cargo_check/help/stdout.term.svg +++ b/tests/testsuite/cargo_check/help/stdout.term.svg @@ -121,11 +121,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_clean/help/stdout.term.svg b/tests/testsuite/cargo_clean/help/stdout.term.svg index 9af234f7b..fa18211cc 100644 --- a/tests/testsuite/cargo_clean/help/stdout.term.svg +++ b/tests/testsuite/cargo_clean/help/stdout.term.svg @@ -69,11 +69,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_config/help/stdout.term.svg b/tests/testsuite/cargo_config/help/stdout.term.svg index a1b954e07..d850db288 100644 --- a/tests/testsuite/cargo_config/help/stdout.term.svg +++ b/tests/testsuite/cargo_config/help/stdout.term.svg @@ -51,11 +51,11 @@ Manifest Options: - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_doc/help/stdout.term.svg b/tests/testsuite/cargo_doc/help/stdout.term.svg index 8c7bc637f..e016f459e 100644 --- a/tests/testsuite/cargo_doc/help/stdout.term.svg +++ b/tests/testsuite/cargo_doc/help/stdout.term.svg @@ -115,11 +115,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_fetch/help/stdout.term.svg b/tests/testsuite/cargo_fetch/help/stdout.term.svg index ea89e7e34..f7bac346a 100644 --- a/tests/testsuite/cargo_fetch/help/stdout.term.svg +++ b/tests/testsuite/cargo_fetch/help/stdout.term.svg @@ -53,11 +53,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_fix/help/stdout.term.svg b/tests/testsuite/cargo_fix/help/stdout.term.svg index 658ad3dfe..0595dd269 100644 --- a/tests/testsuite/cargo_fix/help/stdout.term.svg +++ b/tests/testsuite/cargo_fix/help/stdout.term.svg @@ -129,11 +129,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_generate_lockfile/help/stdout.term.svg b/tests/testsuite/cargo_generate_lockfile/help/stdout.term.svg index fbada69b8..207906121 100644 --- a/tests/testsuite/cargo_generate_lockfile/help/stdout.term.svg +++ b/tests/testsuite/cargo_generate_lockfile/help/stdout.term.svg @@ -47,11 +47,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_help/help/stdout.term.svg b/tests/testsuite/cargo_help/help/stdout.term.svg index b63e33f0d..d9c996b8a 100644 --- a/tests/testsuite/cargo_help/help/stdout.term.svg +++ b/tests/testsuite/cargo_help/help/stdout.term.svg @@ -51,11 +51,11 @@ Manifest Options: - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_init/help/stdout.term.svg b/tests/testsuite/cargo_init/help/stdout.term.svg index e832172a0..ffce64b9e 100644 --- a/tests/testsuite/cargo_init/help/stdout.term.svg +++ b/tests/testsuite/cargo_init/help/stdout.term.svg @@ -69,11 +69,11 @@ Manifest Options: - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_install/help/stdout.term.svg b/tests/testsuite/cargo_install/help/stdout.term.svg index 9b0579cbf..8204c163c 100644 --- a/tests/testsuite/cargo_install/help/stdout.term.svg +++ b/tests/testsuite/cargo_install/help/stdout.term.svg @@ -121,11 +121,11 @@ Manifest Options: - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_locate_project/help/stdout.term.svg b/tests/testsuite/cargo_locate_project/help/stdout.term.svg index b21df68c7..f17bdc2f1 100644 --- a/tests/testsuite/cargo_locate_project/help/stdout.term.svg +++ b/tests/testsuite/cargo_locate_project/help/stdout.term.svg @@ -53,11 +53,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_login/help/stdout.term.svg b/tests/testsuite/cargo_login/help/stdout.term.svg index bab300ed6..a6851fc66 100644 --- a/tests/testsuite/cargo_login/help/stdout.term.svg +++ b/tests/testsuite/cargo_login/help/stdout.term.svg @@ -55,11 +55,11 @@ Manifest Options: - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_logout/help/stdout.term.svg b/tests/testsuite/cargo_logout/help/stdout.term.svg index 34d28d8b6..c7ab3556c 100644 --- a/tests/testsuite/cargo_logout/help/stdout.term.svg +++ b/tests/testsuite/cargo_logout/help/stdout.term.svg @@ -47,11 +47,11 @@ Manifest Options: - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_metadata/help/stdout.term.svg b/tests/testsuite/cargo_metadata/help/stdout.term.svg index 494a95c18..35490724c 100644 --- a/tests/testsuite/cargo_metadata/help/stdout.term.svg +++ b/tests/testsuite/cargo_metadata/help/stdout.term.svg @@ -69,11 +69,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_new/help/stdout.term.svg b/tests/testsuite/cargo_new/help/stdout.term.svg index bd7a3c59c..8423c6d68 100644 --- a/tests/testsuite/cargo_new/help/stdout.term.svg +++ b/tests/testsuite/cargo_new/help/stdout.term.svg @@ -69,11 +69,11 @@ Manifest Options: - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_owner/help/stdout.term.svg b/tests/testsuite/cargo_owner/help/stdout.term.svg index ade9c448f..314c785c5 100644 --- a/tests/testsuite/cargo_owner/help/stdout.term.svg +++ b/tests/testsuite/cargo_owner/help/stdout.term.svg @@ -63,11 +63,11 @@ Manifest Options: - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_package/help/stdout.term.svg b/tests/testsuite/cargo_package/help/stdout.term.svg index 8a0767191..dc560c500 100644 --- a/tests/testsuite/cargo_package/help/stdout.term.svg +++ b/tests/testsuite/cargo_package/help/stdout.term.svg @@ -87,11 +87,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_pkgid/help/stdout.term.svg b/tests/testsuite/cargo_pkgid/help/stdout.term.svg index beee2c2f9..7d0407116 100644 --- a/tests/testsuite/cargo_pkgid/help/stdout.term.svg +++ b/tests/testsuite/cargo_pkgid/help/stdout.term.svg @@ -59,11 +59,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_publish/help/stdout.term.svg b/tests/testsuite/cargo_publish/help/stdout.term.svg index 29ba1e1a5..a0aa87d49 100644 --- a/tests/testsuite/cargo_publish/help/stdout.term.svg +++ b/tests/testsuite/cargo_publish/help/stdout.term.svg @@ -87,11 +87,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_read_manifest/help/stdout.term.svg b/tests/testsuite/cargo_read_manifest/help/stdout.term.svg index 06cb56201..822056c78 100644 --- a/tests/testsuite/cargo_read_manifest/help/stdout.term.svg +++ b/tests/testsuite/cargo_read_manifest/help/stdout.term.svg @@ -51,11 +51,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_remove/help/stdout.term.svg b/tests/testsuite/cargo_remove/help/stdout.term.svg index 7e427d870..553a05cc6 100644 --- a/tests/testsuite/cargo_remove/help/stdout.term.svg +++ b/tests/testsuite/cargo_remove/help/stdout.term.svg @@ -71,11 +71,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_report/help/stdout.term.svg b/tests/testsuite/cargo_report/help/stdout.term.svg index d1db5427f..42d8d2656 100644 --- a/tests/testsuite/cargo_report/help/stdout.term.svg +++ b/tests/testsuite/cargo_report/help/stdout.term.svg @@ -51,11 +51,11 @@ Manifest Options: - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_run/help/stdout.term.svg b/tests/testsuite/cargo_run/help/stdout.term.svg index c4bfa6bb3..acc037fc5 100644 --- a/tests/testsuite/cargo_run/help/stdout.term.svg +++ b/tests/testsuite/cargo_run/help/stdout.term.svg @@ -103,11 +103,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_rustc/help/stdout.term.svg b/tests/testsuite/cargo_rustc/help/stdout.term.svg index d43d6b3bd..e57293864 100644 --- a/tests/testsuite/cargo_rustc/help/stdout.term.svg +++ b/tests/testsuite/cargo_rustc/help/stdout.term.svg @@ -125,11 +125,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_rustdoc/help/stdout.term.svg b/tests/testsuite/cargo_rustdoc/help/stdout.term.svg index 6564f7e7f..9331a1840 100644 --- a/tests/testsuite/cargo_rustdoc/help/stdout.term.svg +++ b/tests/testsuite/cargo_rustdoc/help/stdout.term.svg @@ -123,11 +123,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_search/help/stdout.term.svg b/tests/testsuite/cargo_search/help/stdout.term.svg index 00ca8c7f6..e1df6e099 100644 --- a/tests/testsuite/cargo_search/help/stdout.term.svg +++ b/tests/testsuite/cargo_search/help/stdout.term.svg @@ -57,11 +57,11 @@ Manifest Options: - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_test/help/stdout.term.svg b/tests/testsuite/cargo_test/help/stdout.term.svg index 026a47189..c01b806af 100644 --- a/tests/testsuite/cargo_test/help/stdout.term.svg +++ b/tests/testsuite/cargo_test/help/stdout.term.svg @@ -133,11 +133,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_tree/help/stdout.term.svg b/tests/testsuite/cargo_tree/help/stdout.term.svg index 1e3a4ac86..49c659252 100644 --- a/tests/testsuite/cargo_tree/help/stdout.term.svg +++ b/tests/testsuite/cargo_tree/help/stdout.term.svg @@ -97,11 +97,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_uninstall/help/stdout.term.svg b/tests/testsuite/cargo_uninstall/help/stdout.term.svg index 0f051f912..7c3678d58 100644 --- a/tests/testsuite/cargo_uninstall/help/stdout.term.svg +++ b/tests/testsuite/cargo_uninstall/help/stdout.term.svg @@ -65,11 +65,11 @@ Manifest Options: - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_update/help/stdout.term.svg b/tests/testsuite/cargo_update/help/stdout.term.svg index 5f1b8dbd4..2d9bebf44 100644 --- a/tests/testsuite/cargo_update/help/stdout.term.svg +++ b/tests/testsuite/cargo_update/help/stdout.term.svg @@ -61,11 +61,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_vendor/help/stdout.term.svg b/tests/testsuite/cargo_vendor/help/stdout.term.svg index fe7512192..16ad2af1f 100644 --- a/tests/testsuite/cargo_vendor/help/stdout.term.svg +++ b/tests/testsuite/cargo_vendor/help/stdout.term.svg @@ -63,11 +63,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_verify_project/help/stdout.term.svg b/tests/testsuite/cargo_verify_project/help/stdout.term.svg index b98845098..b79ec1911 100644 --- a/tests/testsuite/cargo_verify_project/help/stdout.term.svg +++ b/tests/testsuite/cargo_verify_project/help/stdout.term.svg @@ -47,11 +47,11 @@ --manifest-path <PATH> Path to Cargo.toml - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_version/help/stdout.term.svg b/tests/testsuite/cargo_version/help/stdout.term.svg index dcecb0414..8d133b9e3 100644 --- a/tests/testsuite/cargo_version/help/stdout.term.svg +++ b/tests/testsuite/cargo_version/help/stdout.term.svg @@ -45,11 +45,11 @@ Manifest Options: - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline diff --git a/tests/testsuite/cargo_yank/help/stdout.term.svg b/tests/testsuite/cargo_yank/help/stdout.term.svg index fc5b6e6da..01cade6a8 100644 --- a/tests/testsuite/cargo_yank/help/stdout.term.svg +++ b/tests/testsuite/cargo_yank/help/stdout.term.svg @@ -61,11 +61,11 @@ Manifest Options: - --frozen Require Cargo.lock and cache to be up-to-date + --locked Ensure the exact dependency versions in Cargo.lock is used - --locked Require Cargo.lock to be up-to-date + --offline Run without accessing the network - --offline Run without accessing the network + --frozen Equivalent to specifying both --locked and --offline