Domen Kožar

Support flags directive in stack.yaml when generating packages

4

Example: https://github.com/input-output-hk/cardano-sl/blob/master/stack.yaml#L5 Most probably depends on #5

Hardcoded base GHC packages

15

Right now stack2nix has GHC 8.0.2 hardcoded in a few places, we should make it configurable.

Resulting into very annoying output coming to the terminal while using the prompt.

Add --check support

2

For CI usage it's useful to have a check if the output matches a certain (committed) file.

Cabal2nix already support revision pinning at library level, it also need `--cabal-revision` flag on cli before stack2nix can be integrated.

Or potentially https://github.com/angerman/Cabal2Nix. The next iteration of stack2nix could get rid of the following bugs: - [cabal conditionals resolving differently in stack vs cabal2nix](https://github.com/input-output-hk/stack2nix/issues/103) - [stackage snapshot can pin "no-revision"](https://github.com/commercialhaskell/lts-haskell/issues/149#issuecomment-406985586)...

Right now, stack2nix just maps haskell system dependencies 1:1 into nixpkgs attribute names. This clearly doesn't work and needs to be rethought at cabal2nix. Right now we're using the following...

Running stack2nix on a folder without stack.yaml results into obscure error

2

``` $ ~/.local/bin/stack2nix . > foo.nix Ensuring cabal2nix version is >= 2.2.1 ... Ensuring git version is >= 2 ... Ensuring cabal version is >= 1 ... stack2nix: Failed with...

conditional packages based on GHC version mismatch between cabal2nix and stack

1

If a cabal file has: ``` if impl (ghc < 8.4) build-depends: ghc-syb-utils ``` Then stack using GHC 8.4.x won't consider it as dependency while cabal2nix will. This results into...

Add a comment to the output with what inputs was the file generated

1

Something like: ``` # Generated by stack2nix 0.1 using: # --revision: 3d0e1e41873b4eacff1fcb153d04c2fa8a7dc467 https://github.com/input-output-hk/cardano-sl.git ... ```