Added a new flag --lockfile-path that allows users to specify a path to lockfile other than the default path <workspace_root>/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 should make --lockfile-path imply --locked
[ ] Shell completions.
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
commented
3 weeks ago
Summary
Original issue: #5707 Implementation: #14326 Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#lockfile-path
Added a new flag
--lockfile-paththat allows users to specify a path to lockfile other than the default path<workspace_root>/Cargo.lock.Unresolved Issues
Future Extensions
No response
Tasks
cargo installshould make--lockfile-pathimply--lockedAbout 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.