Hello again Simon! Top posting to make one general and quick comment on this topic. I am very very interested in this attempt of yours and will look into it in detail later on, so do expect many questions on what you did coming my way ;-) But in the mean time, would you care to read my entry on logging support for MacPorts "action targets" (read, those that drive a port toward its destroot)? http://trac.macports.org/projects/macports/wiki/PortLoggingProposal Following the website redesign, this is my number one priority and would indeed love to spark some interest from our developers base. It is one of the goals of my proposal to use the results of logs to create build result pages & summaries like yours on an automated fashion, as detailed in the Wiki doc, so I hope you'll find it interesting. Regards,... -jmpp On Oct 14, 2007, at 6:00 PM, Simon Ruderich wrote:
Hi all,
I tried creating a small "buildfarm" using my MacBook Pro. I already have some results, but it's just a small test, so please be not too strict with it ;-)
You can find the results here: http://ruderich.com/simon/macports/ But the results are some days old, so it may be possible a port is already fixed. I'm sorry but at the moment I don't have any dates.
It would be nice if some of you could use these results to fix broken ports. I separated fetch failures from build/other failures so they should be easy to fix.
If you have any suggestions/improvements/bugs or questions please tell me.
Thanks, Simon _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev