On Mar 27, 2011, at 11:44 PM, Jordan K. Hubbard wrote: > > Well, if your system is designed to ever allow on-demand package building, it > also suggests that the server side needs to know how to get MacPorts to build > things on its behalf, but that doesn't necessarily imply MPAB and a > mass-building scenario either. >
To atone for my snartky public comments, I'll pass along a suggestion here too: MacPorts is actually quite usable as a build system (based on real world experience with too many). Binary packaging is rather a different issue than building. The idea for lazy, build all variants on demand and cache the "sundae+nuts+bananas" results is dead-on imho. The suggestion is to also pay attention to the recursion necessary to rebuild all the pre-requsites to the lazy "sundae+nuts+bananas" initial request. FOr a first pass, one can maintain "everything" build factories able to produce "sundae+nuts+bananas" variant packages. With recursion, the build factories also become self-maintaining and self-assembling. hth 73 de Jeff _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
