buildsystem stuff

[seth vidal]

On Thu, 2005-05-05 at 12:31 -0400, Dan Williams wrote:
> On Thu, 2005-05-05 at 12:04 -0400, Jeremy Katz wrote:
> > On Thu, 2005-05-05 at 09:37 -0400, Dan Williams wrote:
> > > A couple of comments, some of which I'd even be willing to do the work
> > > for :)
> > > 
> > > 1) CVS/tobuild - Could this code be separated into an XML-RPC client?
> > > So you'd have the Queuer be an XMLRPC server, and clients would connect
> > > to it and feed it build jobs.  For Aurora at least, we're probably not
> > > going to have CVS of this type, and "tobuild" seems somewhat cumbersome.
> > 
> > This was definitely intended as the eventual direction.  But we wanted
> > to get something going quickly, and write a file was far simpler. :-)
> > Especially since at first, there wasn't going to be the need for XML-RPC
> > -- that came later as a need for kicking off the ppc builds.
> > 
> > Any help down this path would definitely be appreciated, otherwise it's
> > at least on my todo list.  The key is to keep the client as simple as
> > possible so that we don't have a big list of deps like you end up with
> > for the beehive client.  Basic python + included modules should be
> > fairly sane, though.  And using the client certs for the fedora account
> > system stuff seems like the obvious auth mechanism then. 
> 
> Ok, I'll try to do this in the next couple days then.  Is there CVS
> somewhere for the scripts?  I don't want to do the work and then do
> manual merges really.
> 

code is in extras-buildsys-temp in /cvs/fedora

look in the dir 'automation' in that module.

If you want the code that does the 2-way auth via ssl certs you should
look at m2crypto. CCing this to icon so he can tell you where to look
for the code.

-sv