-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Renamed optional dependency should use the renamed name #5753
Labels
A-optional-dependencies
Area: dependencies with optional=true
Comments
withoutboats
added
the
A-optional-dependencies
Area: dependencies with optional=true
label
Jul 20, 2018
I agree yeah that this should use the name |
alexcrichton
added a commit
to alexcrichton/cargo
that referenced
this issue
Jul 31, 2018
This commit updates the implementation of renamed dependencies to use the listed name of a dependency in Cargo.toml for the name of the associated feature, rather than using the package name. This'll allow disambiguating between different packages of the same name and was the intention all along! Closes rust-lang#5753
bors
added a commit
that referenced
this issue
Jul 31, 2018
Use listed dependency name for feature names This commit updates the implementation of renamed dependencies to use the listed name of a dependency in Cargo.toml for the name of the associated feature, rather than using the package name. This'll allow disambiguating between different packages of the same name and was the intention all along! Closes #5753
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given a Cargo.toml dependency stated like this:
I expected to be able to turn the dependency on with
cargo build --features dalek
. However, this does not work.cargo build --features ed25519-dalek
does work.I think we should be consistent here in treating the dependency name, not the package name, as the name of this optional dependency.
The text was updated successfully, but these errors were encountered: