On ons, 2005-10-12 at 18:14 -0400, Joshua ChaitinPollak wrote: > The bottom line is, I blew away my host computer's /usr/portage, and > now have to recover it. > > Since the development root filesystem is stored on a desktop machines > harddrive, why not just have it get its own, separate portage tree?
This is how I deal with it: * I never keep distfiles and binary packages in the /usr/portage (PKGDIR and DISTFILES in/etc/make.conf) and use portage snapshots. Then its possible to remove /usr/portage anytime and recover with just untarring the snapshot. This is use ful if you have several people working on the same project and you might want to work on the same portage tree. * Always enter in my chroot environment from a script. The script mounts proc and /usr/portage, chroot and then umounts everything again. * In some occations I run a separate portage tree. (where the host's portage tree is updated from a cron job) -- Natanael Copa -- [email protected] mailing list
