Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Migrate --nix support to use haskell.compiler.ghcXYZ attributes instead of haskell.packages.lts_X_Y #2259
I do not see the reason for this change, and it will break existing stack versions and build configurations. This message seems to be frustrated with a variety of non-fundamental, fixable issues. Please consider this more carefully.
If changes to nix / nixpkgs become too much of a maintenance burden, we may need to consider whether stack will continue having first class support for nix. I am not sure how the nix support would need to be adapted to support this, it may not even be viable to adapt it.
How about bringing up this issue on stackage, or integrating the nix feedback into the curation of stackage?
Ok, this seems to be more like "I don't want stable package sets". Follow lts non-strictly if you do want security updates.
So we do want stable package sets! :)
This seems like an impedence mismatch between how nightlies have been exposed to nix users. If "haskellPackages" is always the latest nightly, then yes, you shouldn't do that if you want reliable builds.
If you want something stable, use lts. If you want something unstable, use nightly. It's that simple.
Ok, lets work with you guys to curate stackage via feedback from nix.
My summary of the issues covered is:
IMHO, these reasons are not sufficient to justify this. That said, I am not a nix user and I don't experience the maintenance burden. These are indeed tricky problems, their resolution isn't trivial. However, I don't see how dropping stackage makes (1) any easier, and we can collaborate to address (2).
Please keep in mind that the stackage process is not set in stone, we are still experimenting with it. Please help us refine the process rather than ditching it.
@mgsloan, to the best of my knowledge, adapting Stack to use the compiler attributes rather than the (obsolete) LTS package set attributes should be a harmless change that won't pose any serious problems. I realize it's inconvenient having to make that switch, and I am sorry about that. We did not take that decision lightly and there was a discussion with various Stackage team members beforehand. Alas, things turned out such that the level of support Nix used to offer seems clearly unsustainable, hence the change.