remove no-revision list#8060
Merged
Merged
Conversation
I do not see any reason for them to exist permanently. I don't feel upstreams should be able to decide whether Stackage uses revisions or not for their package: they are used by cabal-install anyway. Obviously from time to time this may be a useful tool if a revision conflicts with stackage's bounds but it should not be a permanent lever IMHO.
Member
Author
|
(Just to be clear - I think the commit msg is ambiguous - no packages are being removed.) |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This empties the
no-revisions:list - I don't see any good reason we should carry these permanently.Most of the 10 packages there date from the previous decade,
and 2 were added in more recent years: I think they were both intended to be temporary bounds workarounds.
I think this list should be up to Stackage not something that upstream maintainers can impose.