Open judah opened 6 years ago
Actually just run their Setup script?
Isn't that basically the only option? Since shake is designed to pick up new dependencies as it goes, is there a way to inspect the results of running Setup, add them to the mix, and carry on?
Several of these no longer use a custom Setup.hs
. The 3 I checked:
https://github.com/ekmett/gl/commit/dba7d55f35e335bbd535fb93274a39ccd5fc03cc https://github.com/simonmar/happy/commit/f2bef509441b63bed05c05759f463adf18e4f758 https://github.com/jgm/pandoc/commit/e8fba105a5e0d63b5fdbc7505d657eda13a52b59
How should we support packages like
proto-lens
orgl
that generate Haskell modules with a custom Setup file? Allow custom user rules? Actually just run their Setup script?Some specific packages:
happy
,alex
: generate template data-files by compiling and running a program with different CPP flags.pandoc
: installsman
pagesemigroupoids
,comonad
,distributive
: usecabal-doctest
lens
: usescabal-doctest
, and also installs an image to be used by the haddocksentropy
: runs a test C program, not sure for what purposedarcs
: generates a customVersion.hs
module for embedding more specific version information; also custom logic for linking against libiconv, similar to what used to be inhaskeline
gtk2hs
: packages likeglib
usegtk2hs-buildtools:Gtk2HsSetup