gelisam / klister

an implementation of stuck macros
BSD 3-Clause "New" or "Revised" License
132 stars 11 forks source link

Get rid of hpack #111

Closed david-christiansen closed 4 years ago

david-christiansen commented 4 years ago

From my perspective, hpack is causing more problems than it solves.

With common stanzas, the repetetiveness of the cabal file format is much reduced, and I keep having to remember to run hpack when I'm building the project. It's also been causing some intermittent CI issues.

How do you all feel about replacing it with a .cabal file with a common stanza?

gelisam commented 4 years ago

sure, no objection

langston-barrett commented 4 years ago

Sounds fine!

gelisam commented 4 years ago

By the way, my colleague Deech recently released https://hackage.haskell.org/package/cabal-auto-expose, which brings some of the benefits of hpack to cabal files by automatically generating the list of .hs files, we could try using that if manually maintaining the list of files gets tiresome.

david-christiansen commented 4 years ago

I add/remove modules so infrequently that tweaking a line in a file is not a big deal. Hpack actually made this all more annoying for me, because I'd switch branches and forget to re-run it before building, and it'd complain :)