Update specific package building tutorial #867
Merged
Conversation
This file contains hidden or 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
Haskell.nix's `default.nix` is now a function that needs to be called and `hackage-package` can no longer rely on the default internal GHC so `compiler-nix-name` needs to be specified explicitly.
booniepepper
pushed a commit
to booniepepper/haskell.nix
that referenced
this pull request
Feb 4, 2022
Haskell.nix's `default.nix` is now a function that needs to be called and `hackage-package` can no longer rely on the default internal GHC so `compiler-nix-name` needs to be specified explicitly.
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.
Haskell.nix's
default.nixis now a function that needs to be calledand
hackage-packagecan no longer rely on the default internal GHC socompiler-nix-nameneeds to be specified explicitly.This tutorial got outdated. The haskell.nix revision could be pinned to avoid confusion/frustration for new users.
OTOH relying on master means complaints arise sooner and we're forced to keep the examples up to date. Working examples for an old revision would only delay the moment of confusion/frustration to when the users switch to a more recent revision.