build system glue scripts and requirements

[seth vidal]

> * An interface to create a bug according to some "build request form".  
> Simple "new bug" function, got it.
> 
> * An interface to walk through a set of bugs and pull interesting fields.  
> Got it.
> 
> * An interface to add comments to existing bugs.  Got it.

Maybe an interface to lock the bug for a few seconds while you do this
update so two systems don't end up answering at the same time, but I'm
guessing that's implicit.

> And what we don't got, dkl can create, if it's sensible.

sensible is important.


> >  2. Users cannot directly kick off builds, they have to wait (waaaaaaah)
> >  3. Dealing with Embargo'd builds - gonna be a pain no matter what
> >  4. Ordering of builds based on dependency
> 
> How do you do this now?  Is it trial and error, or do you have a heuristic 
> that works?

pass mach a list of related pkgs and it builds them in the right order,
installing the buildreqs it needs for the others it is building in that
set.

So it sounds like the order of operations is:
 - package tracking system
 - xml-rpc interface
 - cvs tagging for extras
 - buildsystem scripts to pull/update this stuff.

sound right?

-sv