On Nov 5, 2005, at 1:01 AM, Philip Lamb wrote:
Originally, I was under the impression that there was a machine autobuilding packages and uploading the binaries. However this is obviously untrue. Does the fink project have the resources to have such an autobuild system established? Ideally, packages would be built as .info files are committed, and so there wouldn't be too much of a massive load.
There exists a tool 'buildfink', written by Matt Sachs at Apple, which essentially attempts to build (and validate) all of Fink. You can find it in our 'scripts' module in CVS. We have the intention of modifying it so it can work with a queue of .info files, at which point it could be used to handle submissions from the tracker and/or commits to a tree. Nobody has gotten around to that yet, but if you'd like to hack on it you're welcome to!
When it comes to a system to perform the builds on, we don't really have anything at this point. A build box should ideally be a very clean system, since we don't want any .debs to be accidentally polluted. Also, we'd have to be careful it's under the control of trusted people, since there's a security risk with distributing binaries. Something to think about once we get sufficient work done on buildfink.
Aside from hacking on buildfink, the best way to help is testing packages. Maybe we should have a 'Test Week', when we ask all developers to NOT write new packages, and instead test various packages out and move them into stable?
Another good thing would be to do more buildfink runs. If anybody has a box that can churn for a week...
Dave
PGP.sig
Description: This is a digitally signed message part
