Improve support for external Hackage repositories #1370
Conversation
This change builds #535. `repository` blocks in `cabal.project` parsed and `cabal` is used to automatically downloaded them. Then `hackage-to-nix` is used to produce the nix required. To make it work with restricted eval (on hydra for instance) we need to include a sha256 like this: ``` repository ghcjs-overlay url: https://input-output-hk.github.io/hackage-overlay-ghcjs secure: True root-keys: key-threshold: 0 --sha256: sha256-EPlLYPmIGtxeahlOspRzwJv+60N5mqrNC2BY4jZKceE= ``` To find the correct `sha256` put in an invalid one and attempt a build.
|
bors try |
tryBuild failed: |
|
bors try |
|
born try- |
|
bors try- |
|
bors try |
Can we do the same thing with the |
tryBuild succeeded: |
|
bors try |
tryTimed out. |
It would be nice if we could have a fixed output derivation that used cabal and nix-tools to get:
It is kind of annoying that |
|
bors try |
tryTimed out. |
Yeah, but even writing an ad-hoc parser in Haskell would be better than doing it in Nix 🙈 |
This change builds on #535.
repositoryblocks incabal.projectparsed andcabalis used to automatically downloaded them. Thenhackage-to-nixis used to produce the nix required.To make it work with restricted eval (on hydra for instance) we need to include a sha256 like this:
To find the correct
sha256put in an invalid one and attempt a build.