[WIP] Update haskell.nix #503
Closed
Conversation
This file contains 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
|
You could also just teach |
|
@michaelpj Isn't it best to use a consistent Nixpkgs pin across the projects? |
|
In theory yes, in practice it has turned out to be infeasible. |
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.
This is necessary for this issue, specifically for the support of Schnorr signatures, as per this PR. As all our SECP256k1 support currently goes via
cardano-base(see this PR), we need access to an updatedlibsecp256k1, which has only been added tonixpkgs-unstablerecently.As this currently depends on this PR landing, I have marked it WIP. Once the
haskell.nixPR lands, I will update to aim athaskell.nixmasterinstead of our fork.