7.2 KiB
3.0.1
-
Fix override with unordered-containers argument,
nothunks
.Added in #26.
3.0.0
-
Add some additional filters to the default
localPkgFilter
argument.Now most files from Haskell.gitignore are filtered out by default.
While this is technically a breaking change, this shouldn't negatively affect most users.
Added in #24.
2.0.1
-
Fixes a bug in the implementation of the new
localPkgFilter
argument added in v2.0.0. This bug is not a correctness problem (so if you accidentally use v2.0.0, you should not get incorrectly built Haskell packages). The bug is just that files will get pulled into the Nix store that you may expect to be filtered out.See #23 for the details.
2.0.0
-
(WARNING: There is a bug in the implementation of this new
localPkgFilter
feature. You are recommended to use v2.0.1 instead of v2.0.0!)Add a
localPkgFilter
argument tostacklock2nix
. This can be used to filter the sources of local Haskell packages.Here's an example of how you might use it:
stacklock2nix { stackYaml = ./stack.yaml; localPkgFilter = defaultLocalPkgFilter: pkgName: path: type: if pkgName == "my-example-haskell-lib" && baseNameOf path == "extra-file" then false else defaultLocalPkgFilter path type; }
This is an example of filtering out a file called
extra-file
from the input source of the Haskell packagemy-example-haskell-lib
.This is a major version bump because if you don't specify the
localPkgFilter
argument tostacklock2nix
, it defaults to using a filter that filters out the.stack-work/
directory, as well as directories likedist-newstyle
. It also passes input files through thelib.cleanSourceFilter
function, which filters out.git/
, as well as a few other types of files.While this is technically a major version bump, most users won't be negatively affected by this change. It is quite likely this won't affect most people.
Added in #22.
1.3.0
-
Add
all-cabal-hashes
as an output fromstacklock2nix
. This can be used as in the "advanced" example:final: prev: { my-example-haskell-stacklock = final.stacklock2nix { stackYaml = ../stack.yaml; all-cabal-hashes = final.fetchFromGitHub { owner = "commercialhaskell"; repo = "all-cabal-hashes"; rev = "9ab160f48cb535719783bc43c0fbf33e6d52fa99"; sha256 = "sha256-Hz/xaCoxe4cJBH3h/KIfjzsrEyD915YEVEK8HFR7nO4="; }; }; my-example-haskell-pkg-set = final.haskell.packages.ghc924.override (oldAttrs: { inherit (final.my-example-haskell-stacklock) all-cabal-hashes; ...
Added in #19.
1.2.0
-
Make sure that
stacklock2nix
will work if the inputall-cabal-hashes
argument is a directory (instead of a tarball).Passing
all-cabal-hashes
as a directory will make the initial build process a little faster (although shouldn't affect future rebuilds).You can easily pass
all-cabal-hashes
as a directory by pulling it down withfetchFromGitHub
like the following:final: prev: { my-stacklock2nix-proj = final.stacklock2nix { stackYaml = ./stack.yaml; ... all-cabal-hashes = final.fetchFromGitHub { owner = "commercialhaskell"; repo = "all-cabal-hashes"; rev = "9ab160f48cb535719783bc43c0fbf33e6d52fa99"; sha256 = "sha256-Hz/xaCoxe4cJBH3h/KIfjzsrEyD915YEVEK8HFR7nO4="; }; }; }
1.1.0
-
Added two new attributes to the attribute set returned from a call to
stacklock2nix
:newPkgSet
andnewPkgSetDevShell
. These two values are similar to the existingpkgSet
anddevShell
attributes. WhereaspkgSet
anddevShell
take thebaseHaskellPkgSet
argument and overlay it with package overrides created from yourstack.yaml
file,newPkgSet
andnewPkgSetDevShell
are a completely new package set, containing only packages from yourstack.yaml
.The effect of this is that
pkgSet
will contain packages that are in Nixpkgs, but not in Stackage. For instance, when usingpkgSet
, you should be able to access the packagepkgSet.termonad
because it is available on Hackage (and in Nixpkgs), even though it is not in any Stackage resolver.However,
newPkgSet
will only contain packages in yourstack.yaml
file. For instance, you'll never be able to accessnewPkgSet.termonad
ornewPkgSet.spago
, because they will likely never be available on Stackage.In general, in your own projects, should you use
pkgSet
ornewPkgSet
?For building your own projects, most of the time
pkgSet
andnewPkgSet
should be similar.newPkgSet
may be slightly safer, since there is almost no chance you accidentally use a Haskell package outside of yourstack.yaml
.pkgSet
may be slightly more convenient depending on what you're trying to do.
1.0.0
-
This is the 1.0 release of
stacklock2nix
. I've testedstacklock2nix
on building a few real-world Haskell projects, and it has worked well.stacklock2nix
is ready to be widely used. -
There have been a some overrides added to
nix/build-support/stacklock2nix/suggestedOverlay.nix
since the 0.2.0 release, but no API changes tostacklock2nix
itself. This would normally be a patch-release (to 0.2.1), but I instead wanted to release version 1.0.
0.2.0
-
Add a
callPackage
argument tostacklock2nix
so that users can easily statically-compile Haskell packages.This could be used like the following:
my-haskell-stacklock = final.stacklock2nix { stackYaml = ./stack.yaml; baseHaskellPkgSet = final.pkgsStatic.haskell.packages.ghc924; callPackage = final.pkgsStatic.callPackage; ... };
-
Make sure
github
types ofextra-deps
instack.yaml
are handled correctly. Previous version did not handlegithub
deps correctly when they had no subdirs.extra-deps
instack.yaml
like the following will now work:extra-deps: - github: "cdepillabout/pretty-simple" commit: "d8ef1b3c2d913a05515b2d1c4fec0b52d2744434"
0.1.0
- Initial release.