Re: [gentoo-dev] Portage through SSH

[John Nilsson]

Some requirement thoughts:
A network of gentoo hosts should have only one portage processing server 
and any number of installation leafs.

First of all portage needs to easily handle more than one installation.
Second the "leaf-installations" should have a very strict minimum 
requiremnts.
Third redundancy is probably important. The information to restore a 
lost "leaf" should be availible on booth the portage host and on the 
leaf it self.

/John

Georgi Georgiev wrote:

> On 31/08/2003 at 17:15:02(+0200), John Nilsson used 2.0K just to say:
>
>>For me the problem is that the machines cant even run emerge sync, much
>>less search for deps and that kind of calculations. I want EVERYTHING
>>portage to be executed on one host (or with distcc a selected few) but
>>still be able to manage the software on the other hosts. Best would be
>>if I could uninstall portage from the other hosts completely.
>
>
> You can mount the remote filesystems over nfs and then set ROOT=/mnt/remote to
> make the portage on the original system install stuff on the remote one. This
> method also has its problems of course. Last time I tried it -- I had lots of
> trouble with for example mplayer autodetecting some libraries on the compiling
> computer that are not installed on the slow host that I was compiling for. Even
> emerge -p was failing because the version of glibc on the compiling system was
> older (only by a release) than the one on the remote system.
> http://bugs.gentoo.org/show_bug.cgi?id=22722
>
> Another thing I tried -- mount the remote filesystems with full permissions,
> chroot over there and start compiling. You may want to "mount -o bind
> /var/tmp/portage /mnt/remote/var/tmp/portage" and also do the same with
> /usr/portage. I of course assume that programs compiled on the slow machine
> would run on the fast one as well (and this is usually the case).
>



--
gentoo-dev@g.o mailing list