Open
Description
I agree with the comments on #3751 – cabal2nix shouldn’t keep growing as new ways to produce a Cabal file appear. It makes sense that the Cabal file is central, and some tools can produce Cabal files while others consume them. So I’m proposing the opposite.
There are two paths here, I think:
- remove all “feature creep” (fetching from git, etc.), such that
hpack - | cabal2nix
(orhpack && cabal2nix
) is sufficient for “hpack support”; or - keep those other pieces, and provide a generic preprocessor hook to run an arbitrary process, like
cabal2nix --pre hpack
orcabal2nix --pre dhall-hpack-cabal
.
While the first option is ultimately simpler, I think it involves larger changes in downstream projects, so the second option seems much more practical.
Footnotes
Metadata
Assignees
Labels
No labels