stackage2nix
stackage2nix copied to clipboard
typeable
Generate Nix build instructions from a Stack file
Unable to build `nix/stackage2nix` on NixOS with [nix.useSandbox](https://nixos.org/nixos/manual/options.html#opt-nix.useSandbox) enabled. > nix.useSandbox > If set, Nix will perform builds in a sandboxed environment that it will set up automatically for each...
I ran into the same problem as reported in https://github.com/typeable/nixpkgs-stackage/issues/38#issuecomment-450816896: `lens` failing to build with a "serious configure-time warning from Cabal " error. I think the problem is that the...
The function `configureCabalFlags` uses a list of packages that should be called with certain flags when passing them to `cabal2nix`. For example, for `hslua`, it specifies that it is to...
The output of `haskell-packages/default.nix` at the moment looks something like this: ```haskell { nixpkgs ? import {} }: with nixpkgs; let ... in callPackage (nixpkgs.path + "/pkgs/development/haskell-modules") { ghc =...
When `stackage2nix` is used alongside `stack`, it is likely that the local packages contain a `.stack-work/` folder. Those can quickly grow in size, and when putting the `src` of the...
I have the following dependencies in my `stack.yaml`: ``` - location: git: [email protected]:arbor/antiope.git commit: ba073b0cd3847f6549960ecdd321259581582146 subdirs: - antiope-core - antiope-s3 extra-dep: true ``` But `stackage2nix` doesn't seem to like it:...
Here is a part of my `stack.yaml`: ``` extra-deps: - avro-0.3.0.4 ``` Running `stackage2nix --with-stackage ./stack.yaml` gives me this error: ``` stackage2nix: user error (No such package avro-0.3.0.4 in the...
Probably that could be filed to nixpkgs repo but maybe it's something of a known issue. I'm using nixos-18.03, trying to install `stackage2nix` with `nix-env -f "" -i -A haskellPackages.stackage2nix`,...
https://github.com/typeable/stackage2nix/blob/17526c82ae05dfd81dc30b247d2b6f95d27369dc/src/Distribution/Nixpkgs/Haskell/Stack/PrettyPrinting.hs#L144 Why does `configurationCommon` takes precedence over the more specific `packageSetConfig` and `compilerConfig`?
Stack is adding new syntax, which should actually be somewhat nicer (and in particular allows pinning of cabal revision). See https://www.fpcomplete.com/blog/2017/07/stacks-new-extensible-snapshots for details.
