Am 18/10/2016 um 09:57 schrieb Adrien Destugues:
Well, that's where it ultimately belongs, doesn't it?We will need policies on who can push to that branch and what the
process is. Since the build of package repos will ultimately be
triggered by pushing to that branch, we need to be reasonably sure
that we don't push too broken things there.
If the Haiku project is fine with leaving this in control of the
HaikuPorts project, I'll move the discussion there. Otherwise, we
could put that branch on Haiku's github repos instead and keep some
control on it.
Also, this morning I've set up a first bot, provided by Arfonzo. It's
currently (slowly) running over the current package list.
From the previous builds I remember some issues we will need to fix:
- gcc_6809 is broken. I suggest removing it from the depot since I'm
likely the only user. I'll fix the recipe later. - avr_gcc is also
broken. It would be nice to fix this one as it is used for Arduino. -
there is a mismatch between mesa_x86 and llvm_x86. I suggest
downgrading llvm to fix mesa build, or updating mesa to match the
current llvm version. Possibly the llvm libs need a version prefix.
On the TODO list is also making more improvements to the build status
page, and moving some of the logic server-side (the current page
downloads several megabytes of JSON and process it in javascript on
user side, it is slow and bulky). We may be able to reuse some of
Kallisti5 and waddlesplash's work here, and maybe put some GCI
students on the job.
