| 1 |
On Sat, 2 Apr 2011 16:19:45 +0100, Peter Humphrey wrote: |
| 2 |
|
| 3 |
> > I've found there's just too much overhead with distcc, plus much of |
| 4 |
> > the work is still done locally. I have a couple of Atom boxes, a |
| 5 |
> > server and a netbook, and I've set up a chroot for each on my |
| 6 |
> > workstation. In the chroot I have FEATURES=buildpkg, using an NFS |
| 7 |
> > mounted PKGDIR available to both computers, then I emerge -k on the |
| 8 |
> > Atom box. |
| 9 |
> |
| 10 |
> Just to confirm, and to save me having to think more deeply than I'm |
| 11 |
> able pro tem, does each chroot have identical make.conf and package.use |
| 12 |
|
| 13 |
Yes. the script that I use to start up and enter the chroot for each |
| 14 |
system not only does the usual mounting of /dev/ and /proc in the |
| 15 |
chroot, it also rsyncs /etc/portage and /var/lib/portage/world* with the |
| 16 |
real target. Make.conf has to be maintained manually, because there are |
| 17 |
settings in the two that need to be different, although I suppose I could |
| 18 |
split out the common settings, USE, CHOST etc, into a separate file and |
| 19 |
source that. |
| 20 |
|
| 21 |
> to those on its target? And do you nfs-mount only the PKGDIR, or the |
| 22 |
> whole of /usr/portage/ ? |
| 23 |
|
| 24 |
Just PKGDIR and DISTDIR, I have an NFS exported directory that contains a |
| 25 |
global DISTDIR and individual PKGDIRS, as well as my and layman's |
| 26 |
overlays. |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
Neil Bothwick |
| 31 |
|
| 32 |
We can sympathize with a child who is afraid of the dark, but the |
| 33 |
tragedy of life is that most people are afraid of the light. |
Archives