1 |
On 31/08/2003 at 17:15:02(+0200), John Nilsson used 2.0K just to say: |
2 |
> For me the problem is that the machines cant even run emerge sync, much |
3 |
> less search for deps and that kind of calculations. I want EVERYTHING |
4 |
> portage to be executed on one host (or with distcc a selected few) but |
5 |
> still be able to manage the software on the other hosts. Best would be |
6 |
> if I could uninstall portage from the other hosts completely. |
7 |
|
8 |
You can mount the remote filesystems over nfs and then set ROOT=/mnt/remote to |
9 |
make the portage on the original system install stuff on the remote one. This |
10 |
method also has its problems of course. Last time I tried it -- I had lots of |
11 |
trouble with for example mplayer autodetecting some libraries on the compiling |
12 |
computer that are not installed on the slow host that I was compiling for. Even |
13 |
emerge -p was failing because the version of glibc on the compiling system was |
14 |
older (only by a release) than the one on the remote system. |
15 |
http://bugs.gentoo.org/show_bug.cgi?id=22722 |
16 |
|
17 |
Another thing I tried -- mount the remote filesystems with full permissions, |
18 |
chroot over there and start compiling. You may want to "mount -o bind |
19 |
/var/tmp/portage /mnt/remote/var/tmp/portage" and also do the same with |
20 |
/usr/portage. I of course assume that programs compiled on the slow machine |
21 |
would run on the fast one as well (and this is usually the case). |
22 |
|
23 |
-- |
24 |
/ Georgi Georgiev / If you see an onion ring -- answer it! / |
25 |
\ chutz@×××.net \ \ |
26 |
/ +81(90)6266-1163 / / |
27 |
|
28 |
-- |
29 |
gentoo-dev@g.o mailing list |