-
Notifications
You must be signed in to change notification settings - Fork 2.9k
RFE: add option to specify path to Cargo.lock #5707
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
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.
In Fedora we package all crate sources (including tests) in
/usr/share/cargo/registrywhich is not user-writable. However, we would like to run tests for them after installation. There is already option fortarget-dirand it would be very nice to get option to put Cargo.lock in some other directory so that we could runcargo testfrom there.