Tracking Issue for `-Zlockfile-path`

[weihanglo]

Summary

Original issue: #5707
Implementation: #14326
Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#lockfile-path

The -Zlockfile-path flag enables the resolver.lockfile-path configuration option,
which allows you to specify the path of the lockfile Cargo.lock.

Unresolved Issues

• How this should work if the lockfile or a parent directory is not present
  • In #14326, missing parent directories will be created when Cargo is about to write the lockfile. This minimizes the chance of creating dangling directories.
• cargo install --config resolver.lockfile-path=<path> implies --locked, and requires the alternative lockfile to exist.
  • This behavior diverges from other commands, which allow the absence of lockfile at the alternative path.
• Allow to set lockfile-path via an environment variable #15510

Future Extensions

No response

Tasks

• Add an unstable doc under https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#lockfile-path doc: add lockfile-path unstable doc section #14423
• cargo install should make --lockfile-path imply --locked feat: lockfile path implies --locked on cargo install #14556
• Add support for resolver.lockfile-path in fix(lockfile): switch to resolver.lockfile-path config #16510
• Remove --lockfile-path in 1.95.0-nightly

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

[ifropc]

@rustbot claim

[ifropc]

As far as shell completions go, I don't think we need to do anything in the scope of this task. In fact, it's alreadyready working on the latest nightly (as part of #14520)