Automatically extract GHC version from cabal.project #13
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
|
As discussed internally, better not to merge this in favour of: |
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 PR defines a function to automatically extract the GHC version from the cabal.project file in the Juvix repository during the installation process. The function,
fetch_ghc_version, fetches the cabal.project file and parses the with-compiler field to determine the GHC version.This ensures we always use the GHC version specified in the cabal.project file, improving the automation of our setup process and reducing potential errors due to GHC version mismatches. ;)
It works well on my machine, but I would strongly recommend testing this before merging.