Any ways to test a GHC build against large set of packages (including test suites)?
Joachim Breitner
mail at joachim-breitner.de
Sat Aug 11 17:48:45 UTC 2018
Hi,
Am Freitag, den 10.08.2018, 20:06 -0400 schrieb Ben Gamari:
> Head.hackage doesn't have an out of the box package set but it is
> quite straightforward to construct such a set. While I now tend to
> use nix, in the past I generally just constructed a dummy cabal
> package listing the packages of interest as dependencies.
>
> There are two approaches to choosing a set of packages: extract the
> packages from Stackage's build-constraints.yaml or just additively
> build up a set from the top of your head. I find the latter is often
> more realistic; stackage is now large enough that even getting a
> fraction of it to build with a prerelease compiler can be a
> significant undertaking.
here is another package set worth considering, if you want a
representative collection of packages with (somewhat) significance: The
packages distributed by Debian:
https://salsa.debian.org/haskell-team/package-plan/raw/master/packages.txt
Cheers,
Joachim
--
Joachim Breitner
mail at joachim-breitner.de
http://www.joachim-breitner.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20180811/3b6783e9/attachment.sig>
More information about the ghc-devs
mailing list