On Mon, 2004-02-09 at 15:49, Konstantinos Agouros wrote: > If not here's how we thought of doing it (comments welcome). > > One machine (the fastest one) keeps /usr/portage. Everybody else mounts this > read only. Once every night (after the rsync) all machine do an emerge -uDp > world and send the result to the server. > > The server has some kind of database knowing the cpu-type and start ebuild- > packaging the necassary packages for each cpu-type. The packages are put in > /usr/portage/packages/<cputype>/All > > Each machine has this mounted to /usr/portage/packages/All corresponding to its > CPU-Type. And can than emerge -u the new packages. > > Machines of a different architecture (ie sun) are handled a little differently. > > The one problem I currently see is determining the order of the emerge -u's or > could I use more than one tbz2-file at once so that portage determines the > order. > > Also we will add some kind of flag for packages where it might be better, > if human intervention happens before upgrading.
It sounds like you need to check out distcc which can spread out the compilation among all the machines, doesn't matter if they are different cpu's. There is also a new streaming distfiles server that seems quite promising and could work for you as well called tsp-cache. http://forums.gentoo.org/viewtopic.php?t=110973&highlight=streaming+file+server And I would also ALWAYS check and pre-approve all package upgrades before letting the machines update themselves, especially for a work environment. You might check out the new portage features regarding /etc/portage/package.mask & package.use where you can create your own masking/unmasking and also individual use flag settings at the package level. http://forums.gentoo.org/viewtopic.php?t=121499 -- Brian <[EMAIL PROTECTED]> -- [EMAIL PROTECTED] mailing list
