Hi there,
I have setup a branch on my fork of HaikuPorts, with only the recipes
currently available in our package repositories (all architectures).
This can be used to experiment on a smaller and hopefully self-coherent
(aka builable from scratch) set of packages.
https://github.com/pulkomandy/haikuports/tree/release
The plan as I see it would be:
1) Set the main buildmaster instance to work from this branch, instead
of working from trunk.
2) Cleanup the branch and get it to work, depending on what issues the
buildmaster raises.
3) Add in more packages from the trunk, but make sure to not break
anything (no broken recipes, correct declaration of architecture
compatibility, etc) - maybe we will need a second instance of the
buildmaster working from trunk.
4) The "release" branch is used to build the official repos for Haiku,
replacing the existing "jam upload-packages" system. It should have the
same (or better) level of QA.
Opinions and suggestions welcome.
Here is the script I used to create the branch:
http://pulkomandy.tk/drop/mkrelbranch.py
It is quite ugly and slow, but I don't think we will need to run this
often in the long term. We will just cherry-pick files from the trunk
and into the release branch.
--
Adrien.
