Hamish Mackenzie

bors try

I think this might be a bug in haskell.nix. If both a `.cabal` file and a `package.yaml` file are present in a directory should we be running `hpack` at all...

I think this has been fixed for `cabalProject` (it now prefers `.cabal` file over `package.yaml` if both are present). I am not sure about `stackProject` though.

Might be worth including the bash stuff in the docs in document tests. It's not actually testing anything in this repo except the documentation itself, but it would still be...

With the addition of `evalSystem` in #1546 it is now possible to be explicit about the eval system and this works when run on an `x86_64-linux` system: ``` nix-build --system...

I used `nix-diff` to compare two of these and the difference between them is the GHC version used to build `cabal-install` and `nix-tools` (haskell.nix defaults to using the project's GHC...

`nix-tools` to truncate the index https://github.com/input-output-hk/haskell.nix/blob/62a4287cac70bd06827844f9470da4eab01719f1/overlays/haskell.nix#L198 `cabal-install` to build a suitable `.cabal` directory using `cabal new-update` https://github.com/input-output-hk/haskell.nix/blob/62a4287cac70bd06827844f9470da4eab01719f1/overlays/haskell.nix#L283 We could delay these steps and run them on demand. If we changed...

CC @newhoggy

@yvan-sraka, I forgot we had this. Very basic and it runs all the tests in one big lump.

I am having trouble understanding what this would be for. Perhaps add an example project (does not have to work) demonstrating a use case?