Skip to content

Conversation

@angerman
Copy link
Collaborator

No description provided.

 #6 included "Per component building, and hackage DB", this
PR only pulls in the relevant hackage-db logic.  The per
component building (nix) will be a separate PR.
@angerman angerman changed the base branch from master to feature/stack-snapshots October 15, 2018 14:17
@angerman
Copy link
Collaborator Author

CI failed, because we added hackage-db. We'll need to regenerate the nix expression. However the haskell.nix/compat/driver likely won't understand the new hackage expressions.

This rather crudely integrates most of the haskell
changes from elvishjerricco/per-component-new-names.
@angerman
Copy link
Collaborator Author

With the recent changes to input-output-hk/hackage.nix#2 and angerman/haskell.nix#2, this now allows us to run

$ nix build -f default.nix hsPkgs.nix-tools.components.exes.cabal-to-nix

and obtain result/bin/cabal-to-nix.

{ BSD-3-Clause = bsd3;
BSD-2-Clause = bsd2;
MIT = mit;
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@angerman Should this change be dropped, so as not to conflict with #11?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep. this is dead :-)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll rebase #11, after this to clean up.

@angerman
Copy link
Collaborator Author

Alight, cachix and travis don't play along well right now, builds successfully on macOS and nixOS.

@angerman angerman merged commit 3306971 into feature/stack-snapshots Oct 30, 2018
@angerman angerman deleted the feature/hackage-db branch October 30, 2018 07:34
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.

3 participants