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 a revamp of our use of
fully static Haskell executables.
The main changes are:
We can now use a newer revision of Nixpkgs
The current revision we're using corresponds to Nixpkgs 20.03
We can now more easily update Nixpkgs
The logic in this repository more closely tracks how
static-haskell-nix
works, so whenever that repository updates Nixpkgs we can pick up the change
here, too.
Note that we cannot currently use Nixpkgs
master
due tothis issue, but once that is
fixed when we can track Nixpkgs
master
more freely.We no longer need to keep track of separate Nixpkgs revisions for
static vs. non-static builds
The two builds can also share dependencies, too. Only the top-level
derivations differ now.
The reason that this doesn't use
static-haskell-nix
directly is because ofcabal2nix
evaluation failures,so this change works by lifting just the minimum logic that we need from
the
static-haskell-nix
repository until we can finally use thatrepository (or Nixpkgs directly when it's upstreamed).