Minimal migration to Cabal-3.6.3.0 #1038
Merged
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 patch makes the minimal changes to compile with Cabal-3.6.3.0.
UPDATE: This also enables compilation with GHC 9.2 (#1040).
Cabal-3.6 intends a semantics of the caret operator
^>=
that is more subtle than expanding it into its version interval.We do not pick up this intention in this patch, but fall back to
Further background:
Distribution.Types.VersionInterval
droppedintersectVersionIntervals
etc. in 3.6 cabal#7916Cabal-3.6 probably also intends a safer handling of pathes (
SymbolicPath
), yet we simply fall back toFilePath
usinggetSymbolicPath
.Questions to reviewer:
hackage-server
side?