Reinstate "forbids" property #781
Merged
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
mosteo
force-pushed
the
feat/provides-no-conflict
branch
2 times, most recently
from
bc92e53
to
732c0fd
Compare
3 tasks
Fabien-Chouteau
approved these changes
Aug 18, 2021
|
It would be good to have "user changes" entry for this. |
mosteo
force-pushed
the
feat/provides-no-conflict
branch
from
45aa4ff
to
6a1787e
Compare
Base automatically changed from
feat/provides-no-conflict
to
merging/toolchains
August 18, 2021 10:59
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.
Fixes #105.
We had this implemented but no way to use it because there was no implementation for loading it from the TOML index. This PR provides this missing load functionality and a couple of tests for it.
The
forbidsfield has the same syntax as thedepends-on. It serves to specify releases (in the form of dependencies) that should not appear in the same solution as the release using theforbidsdeclaration. The two main use cases are to prevent known conflicts (e.g., two crates that have some sources with the same filenames), and to allow drop-in replacements withprovides. In this second case it works the same as conflicts inapt-get: a crate may declare that it both provides and forbids a second crate. This way, it can fill for the provided crate, and no other crate will also be used for the provided crate.