Hi Jappie, This answer will only tangentially answer your question. Head hackage by design is GhC development internal and should never ever leak out of ghc development. As such the packages building with it today may not build tomorrow (ghc HEAD is a moving target).
What you _can_ do is look at the package patches in head.hackage; and the look at the dependencies for them in hackage to get a rough estimate of direct and indirect packages being enabled. Getting an accurate count would require trying to compile all hackage against some ghc from master. And that number likely changes every day due to head of ghc and hackage being moving targets. L A more sensible option might be to try and use a subset like stackage or the CLC stackage set to buidl against. Best, Moritz. On Tue, 23 Jul 2024 at 8:39 AM, jappie klooster <jappiekloos...@hotmail.com> wrote: > Hello everyone, > > For the stability working group I'm trying to understand how many > packages head.hackage allows you to build. > Does anyone know the answer to this or have an idea how I can find out? > > For context, the stability working group is a group of interested people > who try and allow ghc and haskell > system to innovate, while reducing the amount of friction caused to the > wider Haskell community. > Current efforts include the marking language proposals as stable, > and my work of investigating historic breakage. > Investigating this breakage will allow us to make better informed > decisions on which pain points to prioritize. > > > -- > With regards, > > Jappie Klooster > > e: h...@jappie.me > w: https://jappie.me > m: +31644237437 > _______________________________________________ > ghc-devs mailing list > ghc-devs@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs >
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
