-
Notifications
You must be signed in to change notification settings - Fork 247
Provide hackage and stackage from haskell.nix #47
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
Conversation
Thanks for the reviews @angerman @ElvishJerricco. Am I right to say that with |
Yes. They should both be append only. I am however only certain that the hackage index is append only. For stackage I'm only pretty sure that that is the case. I don't remember any formal statement. |
Personally, I'd like to see the necessary modifications made to nix-tools before merging this, so that we don't have the code churn in |
I'm ok with a two step approach. @rvl we don't have the |
I didn't add a script for updating I made the PR input-output-hk/nix-tools#28 so that we can import Once this PR is approved, I plan to squash the rework commits before merging. |
40ebcbb
to
4298181
Compare
I have a suspicion that the compat stuff is bitrotting because it's not being used and there are no tests. Relates to #24
4298181
to
0eac218
Compare
Providing hackage and stackage here simplifies usage of the new Haskell Infrastructure. With this change, the user doesn't need to specify revisions of the external repos, or update them. Basically, with hackage.nix and stackage.nix, the latest version is always best, because snapshots and package versions are added on top. So there is no need for users to choose a revision. Also add mkStackPkgSet which is a shortcut for building stack projects.
e0c9a45
to
7ff3d1a
Compare
Provide hackage and stackage from haskell.nix
Providing hackage and stackage here simplifies usage of the new Haskell Infrastructure.
With this change, the user doesn't need to specify revisions of the external repos, or update them.
Basically, with hackage.nix and stackage.nix, the latest version is always best, because snapshots and package versions are added on top. So there is no need for users to choose a revision.
Add the mkStackPkgSet function which is a shortcut for building stack projects.
Add a test case for stack projects
Add nix-tools
Provide a script which updates
hackage.nix
, pushes the changes, and then updateshackage-src.json
. Also provide a script which likewise updatesstackage.nix
, and a little bit of documentation.