-
Notifications
You must be signed in to change notification settings - Fork 4
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
Freeze the package versions based on the ones from nixpkgs #117
Conversation
This prevents Icepeak from being built using the wrong versions after a `cabal update`. We could disable Hackage completely but that would break non-Nix builds.
dfafbf1
to
9f77477
Compare
I changed the check to just use |
.semaphore/semaphore.yml
Outdated
@@ -43,6 +43,10 @@ blocks: | |||
- echo "max-jobs = auto" >> ~/.config/nix/nix.conf | |||
|
|||
jobs: | |||
- name: "Check frozen versions" | |||
commands: | |||
- "cabal build --dry-run all" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might need a nix develop
- it failed on CI because it cannot find cabal
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right, I forgot there's no devenv there. Should be fixed now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks! @OpsBotPrime merge |
Pull request approved for merge by @robbert-vdh, rebasing now. |
This makes sure the package versions from nixpkgs and the versions specified in the freeze file are in sync.
Approved-by: robbert-vdh Auto-deploy: false
Rebased as 4173a02, waiting for CI … |
CI job 🟡 started. |
be71b32
to
4173a02
Compare
This prevents the plain Cabal and the Nix builds from using different versions. This is especially important when using Nix, as Cabal may start using more up to date versions of the package from Hackage if the user has run
cabal update
before and a local package database exists. Cabal can also be forced to use only the global package registry in which case this problem also doesn't exist, but that requires either breaking non-Nix builds or wrapping thecabal
command.I also added the freeze files to the Nix builds so we'll get alerted if nixpkgs gets updated without also updating the freeze file.