Do not inherit repositories in addons #62
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
An addon repository does not necessarily want the same repos or exclusions as its base, and vice versa. For example, ELN should really not include Extras, and a lot of unwanted packages that we want to filter from Buildroot or Rawhide may still be eligible for ELN Extras.
|
/cc @tdawson |
|
I think this will work. |
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.
An addon repository does not necessarily want the same repos or exclusions as its base, and vice versa. For example, ELN should really not include Extras, and a lot of unwanted packages that we want to filter from Buildroot or Rawhide may still be eligible for ELN Extras.