cargo vendor emits the vendor dir wherever you run it. not at the root of the workspace

Open
#7,110 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
build-system

Research direction

Start by locating the cargo vendor command and the workspace path handling it uses. Check how the current directory, workspace root, and existing vendor directory are selected; done means vendor output consistently follows the requested workspace-root behavior while preserving an existing current-directory vendor directory.

Written by the indexing model from the issue text.

Description

C-bug Command-vendor S-propose-close

Intuitively running cargo vendor would write to the /vendor/ directory at the root of the workspace, where it is most useful. Not inside the a member of the workspace, nor in its /src/ directory.

Possible Solution(s)

Change where vendor attempts to write. To make it less breaking, use the /vendor/ directory from the current directory if it already exists.

Dominant language
Rust
Stars
15.5k
Forks
3k
Avg merge
23h 30m
Merged PRs (30d)
51

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-lang/cargo

All issues in rust-lang/cargo

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.