You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This overlay is amazing! Thank you for doing this. I'm already using it for one of my Haskell projects and I'm planning to integrate it into all of them soon.
It would be even better if you removed all of the <nixpkgs/pkgs/...> path impurities, so that you could pin the nixpkgs used throughout the project. It appears that you only use this for importing functions that nixpkgs doesn't export via pkgs, but it should still make debugging issues much easier since you would know, based on the nixpkgs-stackage revision you're using, which nixpkgs is being used for functions, as well.
I implement this technique in all of my overlays with great success. For example, here is where I create the "fetch nixpkgs" function for one of my overlays:
From the top of my head, I can recall only one nasty place where nixpkgs are referenced directly. It is <nixpkgs/pkgs/development/haskell-modules> in default.nix generated by stackage2nix. Now there is makePackageSet available in the haskell.lib, so we could try to use it instead.
Activity
4e6 commentedon Jan 29, 2018
Nice to hear it, thanks!
From the top of my head, I can recall only one nasty place where nixpkgs are referenced directly. It is
<nixpkgs/pkgs/development/haskell-modules>in default.nix generated by stackage2nix. Now there is makePackageSet available in thehaskell.lib, so we could try to use it instead.4e6 commentedon Jan 29, 2018
I opened the typeable/stackage2nix#47 issue