Skip to content

Call cabal project to nix (now with hackage-truncate) #135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
May 21, 2019

Conversation

angerman
Copy link
Collaborator

No description provided.

@angerman angerman changed the title Angerman/call cabal project to nix Call cabal project to nix (now with hackage-truncate) May 20, 2019
@angerman angerman force-pushed the angerman/call-cabal-project-to-nix branch from fe9b826 to e9f3c28 Compare May 20, 2019 13:21
angerman added 4 commits May 20, 2019 22:58
That is, something like this:

```
nix-build --expr 'with import ./. {}; callCabalProjectToNix { index-state = "2019-04-30T00:00:00Z"; src = /some/path; }'
```

should produce something that can be build with mkCabalProjectPkgSet.
previously the fetchurl would produce a different store path each
and every time as hackage's index is a moving target.  With this
impurity setup, we can ignore this.
@angerman angerman force-pushed the angerman/call-cabal-project-to-nix branch from e9f3c28 to 98ff4f9 Compare May 20, 2019 14:58
@angerman angerman merged commit dfefba5 into master May 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant