-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add version bounds to all dependencies in cabal packages. Refs #119. #193
Merged
ivanperez-keera
merged 14 commits into
nasa:develop
from
ivanperez-keera:develop-version-bounds
Dec 26, 2024
Merged
Add version bounds to all dependencies in cabal packages. Refs #119. #193
ivanperez-keera
merged 14 commits into
nasa:develop
from
ivanperez-keera:develop-version-bounds
Dec 26, 2024
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
The cabal packages do not currently specify all version bounds. This makes hackage complain when we upload packages, and can create stability / installation issues for users. This commit adds lower and upper version bounds for all dependencies.
The cabal packages do not currently specify all version bounds. This makes hackage complain when we upload packages, and can create stability / installation issues for users. This commit adds lower and upper version bounds for all dependencies.
…asa#119. The cabal packages do not currently specify all version bounds. This makes hackage complain when we upload packages, and can create stability / installation issues for users. This commit adds lower and upper version bounds for all dependencies.
…asa#119. The cabal packages do not currently specify all version bounds. This makes hackage complain when we upload packages, and can create stability / installation issues for users. This commit adds lower and upper version bounds for all dependencies.
The cabal packages do not currently specify all version bounds. This makes hackage complain when we upload packages, and can create stability / installation issues for users. This commit adds lower and upper version bounds for all dependencies.
The cabal packages do not currently specify all version bounds. This makes hackage complain when we upload packages, and can create stability / installation issues for users. This commit adds lower and upper version bounds for all dependencies.
ivanperez-keera
changed the title
Add version bounds to all dependencies in cabal packages
Add version bounds to all dependencies in cabal packages. Refs #119.
Dec 26, 2024
Change Manager: Verified that:
|
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.
Add version bounds to all dependencies in the cabal packages, as prescribed in the solution proposed for #119 .
The version bounds are chosen so that Ogma can be installed with GHC 8.4.4, the lowest version supported based on the existing constraints on
base
, and GHC 9.4.8, the highest version supported (based on constraints to other packages, as well as the specifics of the current implementation).