fix(cli): resolve confusion between --frozen
and --locked
@ -639,11 +639,6 @@ See '<cyan,bold>cargo help</> <cyan><<command>></>' for more information on a sp
|
||||
.value_hint(clap::ValueHint::DirPath)
|
||||
.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")
|
||||
.help_heading(heading::MANIFEST_OPTIONS)
|
||||
@ -654,6 +649,11 @@ See '<cyan,bold>cargo help</> <cyan><<command>></>' for more information on a sp
|
||||
.help_heading(heading::MANIFEST_OPTIONS)
|
||||
.global(true),
|
||||
)
|
||||
.arg(
|
||||
flag("frozen", "Equivalent to specifying both --locked and --offline")
|
||||
.help_heading(heading::MANIFEST_OPTIONS)
|
||||
.global(true),
|
||||
)
|
||||
// Better suggestion for the unsupported short config flag.
|
||||
.arg( Arg::new("unsupported-short-config-flag")
|
||||
.help("")
|
||||
|
@ -171,16 +171,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -197,6 +195,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -338,16 +338,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -364,6 +362,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -272,16 +272,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -298,6 +296,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -257,16 +257,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -283,6 +281,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -91,16 +91,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -117,6 +115,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -228,16 +228,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -254,6 +252,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -71,16 +71,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -96,6 +94,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -330,16 +330,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -356,6 +354,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -46,16 +46,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -72,6 +70,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -242,16 +242,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -268,6 +266,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Miscellaneous Options
|
||||
-j N, --jobs N
|
||||
Number of parallel jobs to run. May also be specified with the
|
||||
|
@ -404,16 +404,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -430,6 +428,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -158,16 +158,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -184,6 +182,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Miscellaneous Options
|
||||
-j N, --jobs N
|
||||
Number of parallel jobs to run. May also be specified with the
|
||||
|
@ -84,16 +84,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -110,6 +108,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -128,16 +128,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -154,6 +152,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Miscellaneous Options
|
||||
-j N, --jobs N
|
||||
Number of parallel jobs to run. May also be specified with the
|
||||
|
@ -61,16 +61,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -87,6 +85,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Package Selection
|
||||
-p spec…, --package spec…
|
||||
Package to remove from.
|
||||
|
@ -176,16 +176,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -202,6 +200,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -274,16 +274,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -300,6 +298,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -244,16 +244,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -270,6 +268,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -364,16 +364,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -390,6 +388,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -211,16 +211,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -237,6 +235,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Feature Selection
|
||||
The feature flags allow you to control which features are enabled. When
|
||||
no feature options are given, the default feature is activated for every
|
||||
|
@ -81,16 +81,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -107,6 +105,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -53,16 +53,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -79,6 +77,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Display Options
|
||||
-v, --verbose
|
||||
Use verbose output. May be specified twice for “very verbose”
|
||||
|
@ -49,16 +49,14 @@ 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
|
||||
Requires the Cargo.lock file be up-to-date. If the lock file is
|
||||
missing, or it needs to be updated due to changes in the Cargo.toml
|
||||
file, for example a new dependency is added, Cargo will exit with an
|
||||
error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the
|
||||
Cargo.lock file is up-to-date (such as a CI build).
|
||||
|
||||
--offline
|
||||
Prevents Cargo from accessing the network for any reason. Without
|
||||
@ -75,6 +73,9 @@ OPTIONS
|
||||
May also be specified with the net.offline config value
|
||||
<https://doc.rust-lang.org/cargo/reference/config.html>.
|
||||
|
||||
--frozen
|
||||
Equivalent to specifying both --locked and --offline.
|
||||
|
||||
Common Options
|
||||
+toolchain
|
||||
If Cargo has been installed with rustup, and the first argument to
|
||||
|
@ -1,12 +1,10 @@
|
||||
{{#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`"}}
|
||||
Requires the `Cargo.lock` file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the `Cargo.toml` file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
|
||||
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.
|
||||
It may be used in environments where you want to assert that the `Cargo.lock`
|
||||
file is up-to-date (such as a CI build).
|
||||
{{/option}}
|
||||
|
||||
{{#option "`--offline`"}}
|
||||
@ -24,4 +22,8 @@ offline.
|
||||
{{/if}}
|
||||
|
||||
May also be specified with the `net.offline` [config value](../reference/config.html).
|
||||
{{/option}}
|
||||
{{/option}}
|
||||
|
||||
{{#option "`--frozen`"}}
|
||||
Equivalent to specifying both `--locked` and `--offline`.
|
||||
{{/option}}
|
||||
|
@ -191,15 +191,12 @@ terminal.</li>
|
||||
<dd class="option-desc">Add dependencies to only the specified package.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-add---frozen"><a class="option-anchor" href="#option-cargo-add---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-add---locked"><a class="option-anchor" href="#option-cargo-add---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-add---offline"><a class="option-anchor" href="#option-cargo-add---offline"></a><code>--offline</code></dt>
|
||||
@ -214,6 +211,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
|
||||
offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-add---frozen"><a class="option-anchor" href="#option-cargo-add---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -377,15 +377,12 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-bench---frozen"><a class="option-anchor" href="#option-cargo-bench---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-bench---locked"><a class="option-anchor" href="#option-cargo-bench---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-bench---offline"><a class="option-anchor" href="#option-cargo-bench---offline"></a><code>--offline</code></dt>
|
||||
@ -400,6 +397,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
|
||||
offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-bench---frozen"><a class="option-anchor" href="#option-cargo-bench---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -308,15 +308,12 @@ See <a href="https://github.com/rust-lang/cargo/issues/5579">https://github.com/
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-build---frozen"><a class="option-anchor" href="#option-cargo-build---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-build---locked"><a class="option-anchor" href="#option-cargo-build---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-build---offline"><a class="option-anchor" href="#option-cargo-build---offline"></a><code>--offline</code></dt>
|
||||
@ -331,6 +328,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
|
||||
offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-build---frozen"><a class="option-anchor" href="#option-cargo-build---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -290,15 +290,12 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-check---frozen"><a class="option-anchor" href="#option-cargo-check---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-check---locked"><a class="option-anchor" href="#option-cargo-check---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-check---offline"><a class="option-anchor" href="#option-cargo-check---offline"></a><code>--offline</code></dt>
|
||||
@ -313,6 +310,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
|
||||
offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-check---frozen"><a class="option-anchor" href="#option-cargo-check---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -110,15 +110,12 @@ terminal.</li>
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-clean---frozen"><a class="option-anchor" href="#option-cargo-clean---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-clean---locked"><a class="option-anchor" href="#option-cargo-clean---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-clean---offline"><a class="option-anchor" href="#option-cargo-clean---offline"></a><code>--offline</code></dt>
|
||||
@ -133,6 +130,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
|
||||
offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-clean---frozen"><a class="option-anchor" href="#option-cargo-clean---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -265,15 +265,12 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-doc---frozen"><a class="option-anchor" href="#option-cargo-doc---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-doc---locked"><a class="option-anchor" href="#option-cargo-doc---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-doc---offline"><a class="option-anchor" href="#option-cargo-doc---offline"></a><code>--offline</code></dt>
|
||||
@ -288,6 +285,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
|
||||
offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-doc---frozen"><a class="option-anchor" href="#option-cargo-doc---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -79,15 +79,12 @@ terminal.</li>
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-fetch---frozen"><a class="option-anchor" href="#option-cargo-fetch---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-fetch---locked"><a class="option-anchor" href="#option-cargo-fetch---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-fetch---offline"><a class="option-anchor" href="#option-cargo-fetch---offline"></a><code>--offline</code></dt>
|
||||
@ -100,6 +97,10 @@ mode. Cargo will restrict itself to crates that are downloaded locally, even
|
||||
if there might be a newer version as indicated in the local copy of the index.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-fetch---frozen"><a class="option-anchor" href="#option-cargo-fetch---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -370,15 +370,12 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-fix---frozen"><a class="option-anchor" href="#option-cargo-fix---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-fix---locked"><a class="option-anchor" href="#option-cargo-fix---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-fix---offline"><a class="option-anchor" href="#option-cargo-fix---offline"></a><code>--offline</code></dt>
|
||||
@ -393,6 +390,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
|
||||
offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-fix---frozen"><a class="option-anchor" href="#option-cargo-fix---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -58,15 +58,12 @@ terminal.</li>
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-generate-lockfile---frozen"><a class="option-anchor" href="#option-cargo-generate-lockfile---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-generate-lockfile---locked"><a class="option-anchor" href="#option-cargo-generate-lockfile---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-generate-lockfile---offline"><a class="option-anchor" href="#option-cargo-generate-lockfile---offline"></a><code>--offline</code></dt>
|
||||
@ -81,6 +78,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
|
||||
offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-generate-lockfile---frozen"><a class="option-anchor" href="#option-cargo-generate-lockfile---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -266,15 +266,12 @@ information about timing information.</li>
|
||||
### Manifest Options
|
||||
|
||||
<dl>
|
||||
<dt class="option-term" id="option-cargo-install---frozen"><a class="option-anchor" href="#option-cargo-install---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-install---locked"><a class="option-anchor" href="#option-cargo-install---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-install---offline"><a class="option-anchor" href="#option-cargo-install---offline"></a><code>--offline</code></dt>
|
||||
@ -289,6 +286,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
|
||||
offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-install---frozen"><a class="option-anchor" href="#option-cargo-install---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
</dl>
|
||||
|
||||
### Miscellaneous Options
|
||||
|
@ -428,15 +428,12 @@ terminal.</li>
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-metadata---frozen"><a class="option-anchor" href="#option-cargo-metadata---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-metadata---locked"><a class="option-anchor" href="#option-cargo-metadata---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-metadata---offline"><a class="option-anchor" href="#option-cargo-metadata---offline"></a><code>--offline</code></dt>
|
||||
@ -451,6 +448,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
|
||||
offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-metadata---frozen"><a class="option-anchor" href="#option-cargo-metadata---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -182,15 +182,12 @@ be specified multiple times, which enables all specified features.</dd>
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-package---frozen"><a class="option-anchor" href="#option-cargo-package---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-package---locked"><a class="option-anchor" href="#option-cargo-package---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-package---offline"><a class="option-anchor" href="#option-cargo-package---offline"></a><code>--offline</code></dt>
|
||||
@ -206,6 +203,10 @@ offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-package---frozen"><a class="option-anchor" href="#option-cargo-package---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
|
||||
</dl>
|
||||
|
||||
### Miscellaneous Options
|
||||
|
@ -90,15 +90,12 @@ terminal.</li>
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-pkgid---frozen"><a class="option-anchor" href="#option-cargo-pkgid---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-pkgid---locked"><a class="option-anchor" href="#option-cargo-pkgid---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-pkgid---offline"><a class="option-anchor" href="#option-cargo-pkgid---offline"></a><code>--offline</code></dt>
|
||||
@ -114,6 +111,10 @@ offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-pkgid---frozen"><a class="option-anchor" href="#option-cargo-pkgid---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -151,15 +151,12 @@ be specified multiple times, which enables all specified features.</dd>
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-publish---frozen"><a class="option-anchor" href="#option-cargo-publish---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-publish---locked"><a class="option-anchor" href="#option-cargo-publish---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-publish---offline"><a class="option-anchor" href="#option-cargo-publish---offline"></a><code>--offline</code></dt>
|
||||
@ -175,6 +172,10 @@ offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-publish---frozen"><a class="option-anchor" href="#option-cargo-publish---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
|
||||
</dl>
|
||||
|
||||
### Miscellaneous Options
|
||||
|
@ -81,15 +81,12 @@ terminal.</li>
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-remove---frozen"><a class="option-anchor" href="#option-cargo-remove---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-remove---locked"><a class="option-anchor" href="#option-cargo-remove---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-remove---offline"><a class="option-anchor" href="#option-cargo-remove---offline"></a><code>--offline</code></dt>
|
||||
@ -104,6 +101,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
|
||||
offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-remove---frozen"><a class="option-anchor" href="#option-cargo-remove---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
</dl>
|
||||
|
||||
### Package Selection
|
||||
|
@ -210,15 +210,12 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-run---frozen"><a class="option-anchor" href="#option-cargo-run---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-run---locked"><a class="option-anchor" href="#option-cargo-run---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-run---offline"><a class="option-anchor" href="#option-cargo-run---offline"></a><code>--offline</code></dt>
|
||||
@ -234,6 +231,10 @@ offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-run---frozen"><a class="option-anchor" href="#option-cargo-run---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -304,15 +304,12 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-rustc---frozen"><a class="option-anchor" href="#option-cargo-rustc---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-rustc---locked"><a class="option-anchor" href="#option-cargo-rustc---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-rustc---offline"><a class="option-anchor" href="#option-cargo-rustc---offline"></a><code>--offline</code></dt>
|
||||
@ -328,6 +325,10 @@ offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-rustc---frozen"><a class="option-anchor" href="#option-cargo-rustc---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -285,15 +285,12 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-rustdoc---frozen"><a class="option-anchor" href="#option-cargo-rustdoc---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-rustdoc---locked"><a class="option-anchor" href="#option-cargo-rustdoc---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-rustdoc---offline"><a class="option-anchor" href="#option-cargo-rustdoc---offline"></a><code>--offline</code></dt>
|
||||
@ -308,6 +305,10 @@ See the <a href="cargo-fetch.html">cargo-fetch(1)</a> command to download depend
|
||||
offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-rustdoc---frozen"><a class="option-anchor" href="#option-cargo-rustdoc---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -406,15 +406,12 @@ coming from rustc are still emitted. Cannot be used with <code>human</code> or <
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-test---frozen"><a class="option-anchor" href="#option-cargo-test---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-test---locked"><a class="option-anchor" href="#option-cargo-test---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-test---offline"><a class="option-anchor" href="#option-cargo-test---offline"></a><code>--offline</code></dt>
|
||||
@ -430,6 +427,10 @@ offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-test---frozen"><a class="option-anchor" href="#option-cargo-test---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -222,15 +222,12 @@ single quotes or double quotes around each pattern.</dd>
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-tree---frozen"><a class="option-anchor" href="#option-cargo-tree---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-tree---locked"><a class="option-anchor" href="#option-cargo-tree---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-tree---offline"><a class="option-anchor" href="#option-cargo-tree---offline"></a><code>--offline</code></dt>
|
||||
@ -246,6 +243,10 @@ offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-tree---frozen"><a class="option-anchor" href="#option-cargo-tree---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
|
||||
</dl>
|
||||
|
||||
### Feature Selection
|
||||
|
@ -99,15 +99,12 @@ terminal.</li>
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-update---frozen"><a class="option-anchor" href="#option-cargo-update---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-update---locked"><a class="option-anchor" href="#option-cargo-update---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-update---offline"><a class="option-anchor" href="#option-cargo-update---offline"></a><code>--offline</code></dt>
|
||||
@ -123,6 +120,10 @@ offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-update---frozen"><a class="option-anchor" href="#option-cargo-update---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -68,15 +68,12 @@ only a subset of the packages have changed.</dd>
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-vendor---frozen"><a class="option-anchor" href="#option-cargo-vendor---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-vendor---locked"><a class="option-anchor" href="#option-cargo-vendor---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-vendor---offline"><a class="option-anchor" href="#option-cargo-vendor---offline"></a><code>--offline</code></dt>
|
||||
@ -92,6 +89,10 @@ offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-vendor---frozen"><a class="option-anchor" href="#option-cargo-vendor---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
|
||||
</dl>
|
||||
|
||||
### Display Options
|
||||
|
@ -63,15 +63,12 @@ terminal.</li>
|
||||
<code>Cargo.toml</code> file in the current directory or any parent directory.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-verify-project---frozen"><a class="option-anchor" href="#option-cargo-verify-project---frozen"></a><code>--frozen</code></dt>
|
||||
<dt class="option-term" id="option-cargo-verify-project---locked"><a class="option-anchor" href="#option-cargo-verify-project---locked"></a><code>--locked</code></dt>
|
||||
<dd class="option-desc">Either of these flags requires that the <code>Cargo.lock</code> file be
|
||||
up-to-date. If the lock file is missing, or it needs to be updated, Cargo will
|
||||
exit with an error. The <code>--frozen</code> flag also prevents Cargo from
|
||||
attempting to access the network to determine if it is out-of-date.</p>
|
||||
<p>These may be used in environments where you want to assert that the
|
||||
<code>Cargo.lock</code> file is up-to-date (such as a CI build) or want to avoid network
|
||||
access.</dd>
|
||||
<dd class="option-desc">Requires the <code>Cargo.lock</code> file be up-to-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the <code>Cargo.toml</code> file, for example
|
||||
a new dependency is added, Cargo will exit with an error.</p>
|
||||
<p>It may be used in environments where you want to assert that the <code>Cargo.lock</code>
|
||||
file is up-to-date (such as a CI build).</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-verify-project---offline"><a class="option-anchor" href="#option-cargo-verify-project---offline"></a><code>--offline</code></dt>
|
||||
@ -87,6 +84,10 @@ offline.</p>
|
||||
<p>May also be specified with the <code>net.offline</code> <a href="../reference/config.html">config value</a>.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-verify-project---frozen"><a class="option-anchor" href="#option-cargo-verify-project---frozen"></a><code>--frozen</code></dt>
|
||||
<dd class="option-desc">Equivalent to specifying both <code>--locked</code> and <code>--offline</code>.</dd>
|
||||
|
||||
|
||||
</dl>
|
||||
|
||||
### Common Options
|
||||
|
@ -221,17 +221,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -249,6 +246,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -417,17 +417,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -445,6 +442,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -335,17 +335,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -363,6 +360,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -316,17 +316,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -344,6 +341,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -115,17 +115,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -143,6 +140,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -283,17 +283,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -311,6 +308,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -83,17 +83,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -109,6 +106,11 @@ if there might be a newer version as indicated in the local copy of the index.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -411,17 +411,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -439,6 +436,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -62,17 +62,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -90,6 +87,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -302,17 +302,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -330,6 +327,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Miscellaneous Options"
|
||||
.sp
|
||||
\fB\-j\fR \fIN\fR,
|
||||
|
@ -436,17 +436,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -464,6 +461,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -198,17 +198,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -226,6 +223,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Miscellaneous Options"
|
||||
.sp
|
||||
\fB\-j\fR \fIN\fR,
|
||||
|
@ -121,17 +121,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -149,6 +146,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -154,17 +154,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -182,6 +179,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Miscellaneous Options"
|
||||
.sp
|
||||
\fB\-j\fR \fIN\fR,
|
||||
|
@ -81,17 +81,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -109,6 +106,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Package Selection"
|
||||
.sp
|
||||
\fB\-p\fR \fIspec\fR\[u2026],
|
||||
|
@ -220,17 +220,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -248,6 +245,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -334,17 +334,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -362,6 +359,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -302,17 +302,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -330,6 +327,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -444,17 +444,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -472,6 +469,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -266,17 +266,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -294,6 +291,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Feature Selection"
|
||||
The feature flags allow you to control which features are enabled. When no
|
||||
feature options are given, the \fBdefault\fR feature is activated for every
|
||||
|
@ -105,17 +105,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -133,6 +130,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -62,17 +62,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -90,6 +87,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Display Options"
|
||||
.sp
|
||||
\fB\-v\fR,
|
||||
|
@ -72,17 +72,14 @@ 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.
|
||||
Requires the \fBCargo.lock\fR file be up\-to\-date. If the lock file is missing,
|
||||
or it needs to be updated due to changes in the \fBCargo.toml\fR file, for example
|
||||
a new dependency is added, Cargo will exit with an error.
|
||||
.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.
|
||||
It 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).
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-offline\fR
|
||||
@ -100,6 +97,11 @@ offline.
|
||||
.sp
|
||||
May also be specified with the \fBnet.offline\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-frozen\fR
|
||||
.RS 4
|
||||
Equivalent to specifying both \fB\-\-locked\fR and \fB\-\-offline\fR\&.
|
||||
.RE
|
||||
.SS "Common Options"
|
||||
.sp
|
||||
\fB+\fR\fItoolchain\fR
|
||||
|
@ -45,11 +45,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="244px"><tspan> </tspan><tspan class="fg-cyan bold">-C</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><DIRECTORY></tspan><tspan> Change to DIRECTORY before doing anything (nightly-only)</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="262px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="262px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="280px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="280px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="298px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="298px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--config</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><KEY=VALUE></tspan><tspan> Override a configuration value</tspan>
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 8.0 KiB After Width: | Height: | Size: 8.0 KiB |
@ -179,21 +179,21 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="1450px">
|
||||
</tspan>
|
||||
<tspan x="10px" y="1468px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan>
|
||||
<tspan x="10px" y="1468px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1486px"><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="1486px"><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1504px">
|
||||
</tspan>
|
||||
<tspan x="10px" y="1522px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan>
|
||||
<tspan x="10px" y="1522px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1540px"><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="1540px"><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1558px">
|
||||
</tspan>
|
||||
<tspan x="10px" y="1576px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan>
|
||||
<tspan x="10px" y="1576px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1594px"><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="1594px"><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1612px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
@ -127,11 +127,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1018px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="1018px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1036px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="1036px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1054px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 10 KiB After Width: | Height: | Size: 10 KiB |
@ -125,11 +125,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="964px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1018px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="1018px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1036px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 10 KiB After Width: | Height: | Size: 10 KiB |
@ -121,11 +121,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="928px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="946px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="946px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="964px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="964px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1000px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 10 KiB After Width: | Height: | Size: 10 KiB |
@ -69,11 +69,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="460px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="532px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 5.5 KiB After Width: | Height: | Size: 5.5 KiB |
@ -51,11 +51,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="298px"><tspan class="fg-green bold">Manifest Options:</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="370px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 3.3 KiB After Width: | Height: | Size: 3.3 KiB |
@ -115,11 +115,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="874px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="892px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="892px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="910px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="910px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="928px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="928px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="946px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 9.4 KiB After Width: | Height: | Size: 9.4 KiB |
@ -53,11 +53,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="370px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="370px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="388px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 3.9 KiB After Width: | Height: | Size: 3.9 KiB |
@ -129,11 +129,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1018px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="1018px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1036px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="1036px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1054px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="1054px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1072px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 11 KiB |
@ -47,11 +47,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="262px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="280px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="280px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="298px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="298px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="334px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 3.5 KiB After Width: | Height: | Size: 3.5 KiB |
@ -51,11 +51,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="298px"><tspan class="fg-green bold">Manifest Options:</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="370px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 3.3 KiB After Width: | Height: | Size: 3.3 KiB |
@ -69,11 +69,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="460px"><tspan class="fg-green bold">Manifest Options:</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="532px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 5.2 KiB After Width: | Height: | Size: 5.2 KiB |
@ -121,11 +121,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="928px"><tspan class="fg-green bold">Manifest Options:</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="946px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="946px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="964px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="964px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1000px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 10 KiB After Width: | Height: | Size: 10 KiB |
@ -53,11 +53,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="370px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="370px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="388px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 4.1 KiB After Width: | Height: | Size: 4.1 KiB |
@ -55,11 +55,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="334px"><tspan class="fg-green bold">Manifest Options:</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="370px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="370px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="388px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="388px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="406px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 4.1 KiB After Width: | Height: | Size: 4.1 KiB |
@ -47,11 +47,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="262px"><tspan class="fg-green bold">Manifest Options:</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="280px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="280px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="298px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="298px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="334px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 3.5 KiB After Width: | Height: | Size: 3.5 KiB |
@ -69,11 +69,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="460px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="532px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 5.3 KiB After Width: | Height: | Size: 5.4 KiB |
@ -69,11 +69,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="460px"><tspan class="fg-green bold">Manifest Options:</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="532px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 5.2 KiB After Width: | Height: | Size: 5.2 KiB |
@ -63,11 +63,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="406px"><tspan class="fg-green bold">Manifest Options:</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="424px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="424px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="442px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="442px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="460px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="460px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="478px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 5.0 KiB After Width: | Height: | Size: 5.0 KiB |
@ -87,11 +87,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="622px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="640px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="640px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="658px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="658px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="676px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="676px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="694px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 7.0 KiB After Width: | Height: | Size: 7.0 KiB |
@ -59,11 +59,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="370px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="388px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="388px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="406px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="406px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="424px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="424px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="442px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 4.3 KiB After Width: | Height: | Size: 4.3 KiB |
@ -87,11 +87,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="622px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="640px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="640px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="658px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="658px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="676px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="676px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="694px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 7.1 KiB After Width: | Height: | Size: 7.1 KiB |
@ -51,11 +51,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="298px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="370px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 3.5 KiB After Width: | Height: | Size: 3.5 KiB |
@ -71,11 +71,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="478px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="496px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="514px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="532px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="532px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="550px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 5.2 KiB After Width: | Height: | Size: 5.2 KiB |
@ -51,11 +51,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="298px"><tspan class="fg-green bold">Manifest Options:</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="316px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="334px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="352px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="370px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 3.6 KiB After Width: | Height: | Size: 3.6 KiB |
@ -103,11 +103,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="766px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="784px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="784px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="802px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="802px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="820px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="820px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="838px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 8.2 KiB After Width: | Height: | Size: 8.2 KiB |
@ -125,11 +125,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="964px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1018px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="1018px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1036px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 10 KiB After Width: | Height: | Size: 10 KiB |
@ -123,11 +123,11 @@
|
||||
</tspan>
|
||||
<tspan x="10px" y="946px"><tspan> </tspan><tspan class="fg-cyan bold">--manifest-path</tspan><tspan class="fg-cyan"> </tspan><tspan class="fg-cyan"><PATH></tspan><tspan> Path to Cargo.toml</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="964px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Require Cargo.lock and cache to be up-to-date</tspan>
|
||||
<tspan x="10px" y="964px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--locked</tspan><tspan> Require Cargo.lock to be up-to-date</tspan>
|
||||
<tspan x="10px" y="982px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--offline</tspan><tspan> Run without accessing the network</tspan>
|
||||
<tspan x="10px" y="1000px"><tspan> </tspan><tspan class="fg-cyan bold">--frozen</tspan><tspan> Equivalent to specifying both --locked and --offline</tspan>
|
||||
</tspan>
|
||||
<tspan x="10px" y="1018px">
|
||||
</tspan>
|
||||
|
Before Width: | Height: | Size: 10 KiB After Width: | Height: | Size: 10 KiB |