Distributed tinderboxing

[Mark Linimon]

On Wed, Sep 14, 2005 at 01:37:53PM -0700, Ade Lovett wrote:
> It would certainly be trivial to add a table of  
> {objtree,portstree,package_uri,package_date} quads, and have the  
> actual build scripts poke into that to pull packages in a more  
> optimized manner, but again, I'm not sure this requires a core table  
> change.

If you're really thinking expansively, you can always add another
row for 'buildchain' in case someone ever wants to get so bold as to
experiment with icc vs gcc.

Other topic.  Since my one attempt at a tinderbox is on a now-dead
disk I can't go look myself.  Is there anything like the pointyhat
scripts that takes each error log as it occurs, and reduces it to
an error type?  Given that that happens, we can then think about
adapting portsmon to learn from individual build boxes.  (Or, people
can run their own copy of portsmon, I suppose).

mcl