-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Allow to set lockfile-path via an environment variable #15510
Copy link
Copy link
Closed
Labels
A-lockfileArea: Cargo.lock issuesArea: Cargo.lock issuesC-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`S-acceptedStatus: Issue or feature is accepted, and has a team member available to help mentor or reviewStatus: Issue or feature is accepted, and has a team member available to help mentor or review
Description
Metadata
Metadata
Assignees
Labels
A-lockfileArea: Cargo.lock issuesArea: Cargo.lock issuesC-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`S-acceptedStatus: Issue or feature is accepted, and has a team member available to help mentor or reviewStatus: Issue or feature is accepted, and has a team member available to help mentor or review
Type
Fields
Give feedbackNo fields configured for issues without a type.
Problem
In #14326, the capability to specify an
lockfile-pathwas added to cargo. It would be awesome if this would also possible to configure via an environment variable, similar toCARGO_TARGET_DIR.Proposed Solution
Add the capability to set the lockfile path via a
CARGO_LOCKFILE_PATHenvironment variable.Notes
See also #14421