Urias McCullough wrote:
Yep, setting up a buildbot to build packages is certainly something that several of us have discussed. It does require setting up some infrastructure and scripts, however, and it can be a bit complicated.
I understand, it is complicated enough trying to learn the acronyms some days.
And so, how would you propose building a new version of Haiku which requires and updated ICU package automatically with buildbot? You would have to use an old version of Haiku to compile the new ICU package, and then upload the binary package somewhere in order to build the new Haiku version - which is precisely one of the annoying problems that merits some resolution in the future. Same thing might apply to Mesa, OpenSSL, Freetype, and numerous other packages which are required to even build/boot a working Haiku. - Urias
I would think with a packa manager to update the system, this problem, goes away, as the host build machine can keep itself up to date and in sync, and as I siad, having a target based system build bot, offers the advantage of spotting specific issues with teh compiler etc and potential build breakage. Beyond that, at some point a QA process needs to be implemented and applications need testing. But thats a different discussion for a different time.
Sean