Closed as not planned
Description
- Hard build-time library dependencies like
json
can be specified as[dependencies]
, to be installed whencargo build
executes. - Hard built-time dependencies like
thrift
can be specified as[build-dependencies]
, to be installed whencargo build
executes. - Test-time dependencies like
quickcheck
can be specified as[dev-dependencies]
, to be installed whencargo 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.