Las
`source-repository-package` doesn't allow anything not fetchable by Cabal, i.e. - Non-git - Private repository - Source generated by Nix In addition, it's a pain, and not easy to manage when...
I don't see how such a package repository would work without something like hackage.nix specialised to it.
I am a Nix zealot, so I am quite biased, but I imagine you could define the repository in pure Nix, such that it works (only) with `exactDeps = true;`.
@michaelpj This is another issue with `source-repository-package`: `exactDeps` doesn't work with it unless you don't have it in the shell and only while building the shell.
I don't think that's just your opinion, that's the state of `haskell.nix`. I do concede that what I ultimately want is not `haskell.nix`, but something much more lightweight that rather...
@angerman @michaelpj Forgot to note this, but do note that `pkg-def-extras` can not be used for this, as it doesn't effect plan generation, hence the IFD will fail and complain...
We had some issues with the above too, due to implicit ordering of hackages based on their names, which lead to Hackage taking precedence over the custom Hackage, meaning the...
@michaelpj That would really be great. Do you plan to do something like the hackage.nix repo or something else?
Also, I think we can remove pkg-def-extras, since it has no use AFAICT?
You can use https://github.com/mlabs-haskell/haskell-nix-extra-hackage to solve this, but it will not work for non-Nix users obviously.