Skip to content

Command for specifically installing dev-dependencies #6196

Closed as not planned
Closed as not planned
@mcandre

Description

@mcandre
  • 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Command-install

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions