Brandon Allbery via ghc-devs <[email protected]> writes:

> FWIW what I've heard from packagers over the years is that Hadrian is an
> unwanted pain point for them.
>
While I have heard similar things about Hadrian, it does not seem to me
that Buck2 is going to be better in this regard. While I am certain that
Buck2 has many merits, as far as I can tell it is not maintained in a
way to make it easy to consume by open-source packagers or potential
dependees:

* The project does not appear to have a versioning scheme beyond datestamps

* as far as I can tell there are no formal release notes or changelogs
  provided; CHANGELOG.md is, amusingly, only 28 bytes long containing
  the string "- Initial version"

* the GitHub release artifacts [1] themselves are a collection of files
  with neither descriptions nor, in many cases, file extensions

* it appears [2] that there is currently no formal release process
  and the recommended practice appears to be use the tip of `main`

This does not strike me as the sort of package you would want to take as
a dependency outside of a monorepo. As far as I can tell, the only
packaging of Buck2 provided with a formal OS distribution is in
`nixpkgs`. I think that this is quite symptomatic of the problem.

All of this is to say that Buck2 isn't something that I would feel
comfortable telling GHC's packagers that they need to package and
consume. It is already hard enough to get people to package a compiler
like GHC; then demanded that they *also* package a build system which
isn't maintained in a FOSS-friendly manner is only going to exacerbate
this problem.

Naturally, this could change if Buck2's maintenance changes. However,
until then I would be opposed to going this direction regardless of
whatever merits the build system itself might offer.

Cheers,

- Ben


[2] https://github.com/facebook/buck2#-warning---rough-terrain-lies-ahead

Attachment: signature.asc
Description: PGP signature

_______________________________________________
ghc-devs mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to