Neil Bothwick <neil <at> digimed.co.uk> writes: > > On Thu, 24 Mar 2005 17:13:09 -0800, Grant wrote: > > > A little while ago Neil turned me on to quickpkg. It sounds like a > > great way to protect yourself from the new package blues. Is anyone > > using it like that? What would be the best way to assure that your > > system always has a backup copy of your current version of a package > > available before emerging a new one? > > A more reliable method, assuming you have the drive space, is to add > buildpkg to FEATURES in make.conf. Then emerge will automatically build a > package when installing a package. It also means the package is verified, > because ebuild builds it then installs from the package it just built, not > the files in $PORTAGE_TMPDIR.
OK, so I can run distccd on a group of gentoo boxes (AMD athlons/P3/P4) and build one set of binaries to distribute to the others, via cron scheduling. They would point to the one (quickpkg)master (cron-based-rsync)? Any ideas/packages for this, so I don't botch it? Surely with all stage 1 ebuilds, there's got to be an easy,low bandwidth option for management of gentoo systems groups? -- gentoo-user@gentoo.org mailing list