Okay, so I was talking with Patrick, and he said “you should blog this!” and I thought, eh, maybe… so I’ve decided to go ahead and do it, perhaps someone out there will actually implement it while I work on other things and I can benefit from the fruits of their labor
First off, issues that tend to crop up, keywording packages. Sure some arches are more responsive than others, and you can usually keyword it ~ if you have the hardware and can test it… but what if you don’t? You have a few different options - you can find someone who does, and beg them to do it, you can open a bug and beg them to do it, you can join an irc channel and beg them to do it, you can request an account on a box that infra controls and see if it works and do it…
I sumit… my idea…
Koji, Mock, and Xen.
Koji and Mock are a couple of Fedora projects that ease building of packages, with a web interface to request and see the status of builds… creating chroots to do so…
What if you took it a step further with Xen? You could then use domU’s to run the various arches (I think - this is just an idea, I have no idea of the feasibility of it, comments are more than welcome to flesh it out!) and get things compiled and keyworded…
But you could also take it a step further. You could integrate it into Bugzilla as well, perhaps even submitting ebuilds themselves to be tested to the build machine(s). Automatically submit bugs for keywording requests including the logs and possibly the package(s) as well so that rather than having the developer keyword it on his machine, he can install the binary package, and USE the program to see if it works without waiting for the package to compile…
Another usage would be… BINHOST - Gentoo’s portage DOES support installing from binary packages, and its quite easy to do so as long as you keep everything built with the same settings as whatever the BINHOST uses. So these packages could be synced somewhere for *anyone* to download and use as well. Which would give the packages more testing (since sometimes a developer of an arch might have no idea what to do to even test the package, but a user out there might want to - might even have already keyworded it on their machine and are already using it but hadn’t tested it. Along with the web interface, you could perhaps submit that you use the package, and any issues with it - if there are any bugs associated with it, these comments would get forwarded to the appropriate bug….
Thoughts? Comments?