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
Future Extensions
No response
Tasks
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.
Summary
Original issue: #5707
Implementation: #14326
Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#lockfile-path
The
-Zlockfile-pathflag enables theresolver.lockfile-pathconfiguration option,which allows you to specify the path of the lockfile
Cargo.lock.Unresolved Issues
resolvertable being applied tocargo installcargo install --lockfile-path=<path>implies--locked, and requires the alternative lockfile to exist.lockfile-pathvia an environment variable #15510Future Extensions
No response
Tasks
cargo installshould make--lockfile-pathimply--lockedfeat: lockfile path implies --locked on cargo install #14556resolver.lockfile-pathin fix(lockfile): switch toresolver.lockfile-pathconfig #16510resolver.lockfile-pathcoverage in fix(lockfile-path): Respect the config in fix, install #16617--lockfile-pathin 1.95.0-nightlyAbout 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.