-
Notifications
You must be signed in to change notification settings - Fork 115
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
Please, provide an executable with GHC 8.10 in Nixpkgs #656
Comments
Well, since executable is in a bad state, maybe we need to worry about that more, at the moment there is almost no sense in shipping it. I again arrived at the same conclusion I arrived at in #328 |
What are the problems with the current state? Do we have tickets that track them? |
Well, it is very simple, Nixpkgs defaults to 8.8.3, so no executable for us there. In time forming a separate executable - should solve this properly, then we can say - that people opted-in to have the binary, so lets send GHC 8.10 stack then. |
Or maybe we can do a clever hack, and form a separate build of executable, but when we ready - the forming executable is a proper way. |
This was done in Nixpkgs quite some time ago, 8.10.1-specific package there provides HNix executable from the last version and onward. |
Currently the default package for HNix
0.9.0
inhaskell-updates
is without an executable, because Nixpkgs default is 8.8.3.I would go downstream and would try to negotiate the HNix shipment with GHC 8.10 in the closure.
Since that is also a future-proofing, Nixpkgs and we anyway would roll onto GHC 8.10, and executable status would most probably be as true case then as it is now.
The text was updated successfully, but these errors were encountered: