On Tue, 5 May 2009 10:27:52 -0400 Simon <turne...@gmail.com> wrote: ... > Right now, here's the base of the process to get one PC updated > (without my unison world): > host> emerge --sync > host> emerge -uDN sum(worlds) [builds binpkgs] > <sync host's portage with PC's portage> > PC> emerge -uDN -k world > ----- > > Here's the process ( a bit more complicated ) using unionfs: > host> emerge --sync > host> emerge -uDN world > <start unionfs over the whole root and chroot in union mount point> > host> emerge -uDN -k sum(worlds) > <exit chroot> > host> rsync -ah --progress /path/to/rootunionfs/usr/portage/packages/* > /usr/portage/packages/ > host> rm -Rvf /path/to/rootunionfs > <sync and emerge on PC as with previous method> > ---- ... > What do you think? Should i start working on this? Or is there > anything better out there?
Storage space comes pretty cheap these days, so prehaps it's just easier to get dirt-cheap 80G harddisk and build (and keep) all the packages from sum of the worlds on it in a dedicated chroot or VM? To sync world, make.conf and /etc/portage you can easily use distributed VCS like git or mercurial, keeping each host's files in separate branche on this server. It has added benefit of keeping all the history of your configuration, should you need to fall back to some stable state. Also, it's much easier to sync any changes in any way between the hosts that way. sshfs (prehaps with something like funionfs if you keep local packages too) should be enough to mount generated packages to any host and deploy them. To avoid unnecessary syncing of portage trees (even with one local server) you can just mount it when needed, along with the packages, since it doesn't need write access anyway. -- Mike Kazantsev // fraggod.net
signature.asc
Description: PGP signature
