Moving head.hackage upstream

Ryan Scott at
Mon Jul 15 12:14:17 UTC 2019

Count me among the people who are eagerly awaiting this move. If I
understood Ben correctly when discussing this idea with him on #ghc, then
one of the benefits of having head.hackage on GitLab would be that the
head.hackage index would automatically regenerate any time a commit lands.
This would make things far more streamlined than the status quo, where the
index has to be regenerated by hand.

If head.hackage is migrated over to GitLab, would that change how people
are expected to use it? That is, would it still be as simple as copying the
repository stanza from [1] into one's cabal.project file? Or would that
change with a move to GitLab?

Ryan S.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the ghc-devs mailing list