Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command for specifically installing dev-dependencies #6196

Closed
mcandre opened this issue Oct 20, 2018 · 2 comments
Closed

Command for specifically installing dev-dependencies #6196

mcandre opened this issue Oct 20, 2018 · 2 comments
Labels
C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` Command-install

Comments

@mcandre
Copy link

mcandre commented Oct 20, 2018

  • Hard build-time library dependencies like json can be specified as [dependencies], to be installed when cargo build executes.
  • Hard built-time dependencies like thrift can be specified as [build-dependencies], to be installed when cargo build executes.
  • Test-time dependencies like quickcheck can be specified as [dev-dependencies], to be installed when cargo test executes.

But how about soft build-time dependencies like cargo-script supposed to be managed with Cargo.toml, that are not imported by any Rust code but still required for shell commands?

Could we get a cargo subcommand or flag to forcibly install all [dev-dependencies], regardless of whether the dependency is referenced by an extern crate or not?

As a workaround, I am currently managing these kinds of development dependencies by manually executing cargo install <dependency>, but I would prefer to manage these with the same Cargo.toml file as everything else.

@alexcrichton alexcrichton added the C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` label Oct 21, 2018
@autoferrit
Copy link

Has there been any kind of feature added for this since this issue was opened?

@epage
Copy link
Contributor

epage commented Oct 24, 2023

This is a little confusing to read as its using terms from other ecosystems (you don't "install" dependencies). I'm assuming what is wanted is the ability to make bin dependencies available. In light of that, it appears to be a duplicate of issues like #5120 and #2267. Closing in favor of those. If there is a reason we should re-evaluate this, let us know!

@epage epage closed this as not planned Won't fix, can't repro, duplicate, stale Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` Command-install
Projects
None yet
Development

No branches or pull requests

4 participants