rename it from an alternative lockfile name, and put it back.
Overrides `-u` etc.
- * `--no-lock` | `--lock` (default): Whether to take the
- nailing-cargo lock. Some kind of protection against concurrent
- operation is necessary to prevent multiple instances of
+ * `--no-concurrency-lock` | `--concurrency-lock` (default): Whether
+ to take the nailing-cargo lock. Some kind of protection against
+ concurrent operation is necessary to prevent multiple instances of
nailing-cargo trashing each others' work, and possibly mangling
- your `Cargo.toml`s, `Cargo.lock`, etc., so `--no-lock` is dangerous
- unless you take other measures against concurrent execution.
+ your `Cargo.toml`s, `Cargo.lock`, etc., so `--no-lock` is
+ dangerous unless you take other measures against concurrent
+ execution.
* `-h` | `--help`: Print usage summary.
--just-linkfarm | --clean-linkfarm | --keep-linkfarm (default)
--no-nail Do not nail, just run the command.
--no-cargo-lock-manip Do not manipulate Cargo.lock.
- --no-lock Do not take the concurrency lock.
+ --no-concurrency-lock Do not take the concurrency lock.
-s<subcommand> Treat command as `cargo <subcommand>`
--subcommand-props=<prop>,... Override command props (see docs)
$do_nail = !$1;
} elsif (m{^--(no)?-cargo-lock-manip$}) {
$do_cargo_lock = !$1;
- } elsif (m{^--(no)?-lock$}) {
+ } elsif (m{^--(no)?-concurrency-lock$}) {
$do_lock = !$1;
} elsif (m{^--leave-nailed$}) {
$leave_nailed = 1;