-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Include public/private dependency status in cargo metadata #14502
Copy link
Copy link
Closed
Labels
C-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`Command-metadataS-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 reviewZ-public-dependencyNightly: public-dependencyNightly: public-dependency
Metadata
Metadata
Assignees
Labels
C-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`Command-metadataS-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 reviewZ-public-dependencyNightly: public-dependencyNightly: public-dependency
Type
Fields
Give feedbackNo fields configured for issues without a type.
Problem
related to rust-lang/rust#44663
Information about whether or not a dependency is public is not included in the output of
cargo metadata.This could be useful for custom subcommands.
cargo override, would find this useful for eopb/cargo-override#121Proposed Solution
When
-Zpublic-dependencyis enabled, include a boolean flag incargo metadatas output atpackages[].dependencies[].public.If
-Zpublic-dependencyis not enabled, this flag should not appear incargo metadataoutput.Notes
If this feature request is accepted, I'm happy to claim and take a crack at working on it