On Wed, Dec 1, 2010 at 2:53 AM, R P Herrold <[email protected]> wrote: > On Wed, 1 Dec 2010, Douglas Hubler wrote: > >> * Use mock utility now instead of installing rpms after building. >> Cannot say how amazing this tool is (thank you Russ H.!), almost as >> amazing as it is slow the first time you warm the yum cache. mock is >> also invaluable to testing rpm specs and dependencies before >> production installation. Unfortunately rpm builds are order of >> magnitude slower, but the benefits are worth it. > > Usually a local 'lookaside cache' is added as a first step > when buildsystem speed gets important.
as the first step, mock v0.6 that comes w/centos didn't have a lot of the caching plugins, so i pulled a newer version from rpmforge. I struggle with how to make the output from the last rpm build output available as a yum repository to the build of the next rpm. By making a yum repo available, the build can pull in what it needs automatically reading the BuildRequires tags. I though it would make sense to mount a local dir and make that available to the chroot, but I'm not sure. Do you have any suggestions? > Other approaches > outside of 'mock' for setting up a reliable and known > buildroot even faster. [We use a 'distcc' farm for compiles on > a different product, at -j8, locally cutting times by a factor > of to perhaps a quarter of a simple -j2 compile -- some link > time loss when it has to go single thread, but not much] great, I can see this can scale w/the right setup. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
