cargo vendor should have a separate option to choose where to output the .cargo/config
Open
Nobody has claimed this yet.
A-documenting-cargo-itself
C-feature-request
Command-vendor
S-needs-design
- Dominant language
- Rust
- Stars
- 15.5k
- Forks
- 3k
- Avg merge
- 23h 30m
- Merged PRs (30d)
- 51
Description
Currently, the choice is between:
cargo vendor path
printing out
Downloading crate
...
Vendoring crate ...
To use vendored sources, add this to your .cargo/config for this project:
[source.crates-io]
replace-with = "vendored-sources"
...
and
cargo vendor --quiet path
which outputs... nothing. At all.
There should be a way to reliably get that .cargo/config snippet somehow.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the cargo vendor command and its existing --quiet handling to find where the configuration snippet is generated or suppressed. Define the new output-selection option and verify that it reliably emits the .cargo/config snippet without depending on general command verbosity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100