-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
top-level/release-haskell.nix: test static linking as well #124025
top-level/release-haskell.nix: test static linking as well #124025
Conversation
This way we can keep track of any new regressions to this as well as have some binary cache, so using this infrastructure doesn't require compiling GHC all the time.
# test some statically linked packages to catch regressions | ||
# and get some cache going for static compilation with GHC | ||
pkgsStatic.haskellPackages = { | ||
inherit (staticHaskellPackagesPlatforms) |
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.
any suggestions on changes to this list? It shouldn't be too big, but some packages which are a) important and b) unlikely to break (or will degrade the quality of haskellPackages significantly if they break). Also maybe some kind of smaller tool which is a bit more complicated than hello
could be a good idea.
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.
not sure if that fits, but pandoc
came to my mind
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.
but probably not exactly a "small" tool..
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.
I think this list looks good for now.
In #122586 (comment), @rnhmjoj mentioned an issue about packages using TemplateHaskell. I wonder if lens
uses TemplateHaskell anywhere.
Well, I'll go ahead and merge this in, and we can see what happens.
This way we can keep track of any new regressions to this as well as
have some binary cache, so using this infrastructure doesn't require
compiling GHC all the time.
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)