Compatibility with Cabal 2.2 and hpack 2.28 #343
Closed
+127
−38
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
|
Sigh, I just noticed this was already and my fork was simply out of date. |
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.
This introduces compatibility with
Cabal2.2 andhpack2.28. There were a few interesting changes:Cabal'sFlagAssignmentis now a distinct typeCabalnow has a newparsec-based package description parserCabalnow provides variousNFDatainstances which were previously defined as orphans.Cabal's licenses are now given as SPDX nameshpackrefactored various interfacesCompatibility with older
Cabalreleases has been preserved.