Cargo.toml: Specify optional dependencies with dep: prefix #48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Although specifying optional dependencies without the dep: prefix works fine for cargo-level packaging, some OS package managers interpret these as features rather than optional dependencies. As such, explicitly stating that they are optional dependencies will make the packaging process easier. Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm packaging this crate for fedora. Although specifying optional dependencies without the
dep:prefix works fine for cargo-level packaging, some OS package managers interpret these as features rather than optional dependencies. As such, explicitly stating that they are optional dependencies will make the packaging process easier.