Repository navigation
Add cargo lucifer subcommand #6666
Description
Add a new subcommand that brings light (get it?) to cargo's dependency resolving, answering questions like
- Why was that dependency included?
- Why was that feature on this dependency enabled?
- Which other versions were considered and why was this one chosen?
Yes, I made this issue because I saw the last issue was number 6665. Feel free to close it as "bad joke".
Activity
dwijnand commentedon Feb 14, 2019
I dig the joke 😄
Could this use case be satisfied by documenting something along the lines of
RUST_LOG=cargo::ops::resolve=info cargo generate-lockfile?spacekookie commentedon Feb 14, 2019
To propose a bikeshed here, I think it should be called
cargo cultkillercup commentedon Feb 14, 2019
@dwijnand Maybe
env RUST_LOG=cargo::core::resolver=trace cargo generate-lockfileif it was more pretty :Ddwijnand commentedon Feb 14, 2019
This is how I map log levels:
traceI'm deeeep in this module, give me lots of detailsdebugI'm a cargo dev, give me the general-sense detailed log for this moduleinfoI'm a cargo user, looking some more info from the operations in this moduleBut actually, make this detail (or some of it) should be printed by
cargo generate-lockfile -v.epage commentedon Oct 31, 2023
cargo treeI think solvescargo tree -i)cargo tree -e features)As for "what other versions and why this one", that gets complicated with a lot of information involved. Not really seeing a way around that than
env CARGO_LOG=cargo::core::resolver=trace cargo generate-lockfile.Probably the main thing left is documenting these resources somewhere. Like the section of the documentation on the resolver.
docs(ref): Highlight commands to answer dep resolution questions
Auto merge of #12903 - epage:docs-deps, r=weihanglo