The builders are indeed great to QA what comes into the haikuports master branch. Though I wouldn’t trust the repo it generates yet (for instance, policy checks aren’t enforced, which is OK for testing, perl modules are broken). A beta repo will probably happens on its own branch with a full rebuild.
1 reply
Yes, I think I will test on a separate installation. Once the beta branch is created, is the aim to have haikuporter contributors test out the builds on the master branch (in a separate install) and then someone will merge from there to the beta branch when packages are tested? (a bit like Debian testing to stable?)
Chris
1 reply
I am going to experiment using the current package repos to see how it feels with regard to stability and problems encountered. According to that we can decide wether to use the repo directly, or have a stable/testing approach. Since there is already a review when merging pull requests to the main repo, it may not be needed, but I want to make an opinion on that by testing the repos to see what happens.
My journey did not start too well: beam does not start, so first I’ll need to fix that recipe.
