public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@humphrey.ukfsn.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] distcc and crossdev, anyone?
Date: Sun, 3 Apr 2011 14:55:39 +0100	[thread overview]
Message-ID: <201104031455.39722.peter@humphrey.ukfsn.org> (raw)
In-Reply-To: <20110402234742.61bb6e41@zaphod.digimed.co.uk>

On Saturday 02 April 2011 23:47:42 Neil Bothwick wrote:

> Yes. the script that I use to start up and enter the chroot for each
> system not only does the usual mounting of /dev/ and /proc in the
> chroot, it also rsyncs /etc/portage and /var/lib/portage/world* with the
> real target. Make.conf has to be maintained manually, because there are
> settings in the two that need to be different, although I suppose I could
> split out the common settings, USE, CHOST etc, into a separate file and
> source that.

In my case the chroot is identical in structure to the real target, apart from 
the number of cores, so I can copy make.conf into the chroot without risk.

> > to those on its target? And do you nfs-mount only the PKGDIR, or the
> > whole of /usr/portage/ ?
> 
> Just PKGDIR and DISTDIR, I have an NFS exported directory that contains a
> global DISTDIR and individual PKGDIRS, as well as my and layman's
> overlays.

I'm hoping not to have to use any overlays here, mostly because the target box 
is going to be a LAN server, so shouldn't need any cutting-edge versions of 
anything.

My setup mounts /usr/portage over nfs from the target; it's going to contain the 
latest tree for rsync'ing clients from, so it's the master version.

Interesting - many thanks. It's all getting quite involved.

-- 
Rgds
Peter



  reply	other threads:[~2011-04-03 13:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-17 22:56 [gentoo-user] distcc and crossdev, anyone? Peter Humphrey
2010-12-17 23:23 ` Jacob Todd
2010-12-18 15:22   ` Peter Humphrey
2010-12-17 23:24 ` Al
2010-12-18  8:44 ` Stroller
2010-12-20 15:31   ` Paul Hartman
2010-12-18 10:18 ` Neil Bothwick
2010-12-18 15:15   ` Peter Humphrey
2010-12-20 23:56     ` Bill Longman
2010-12-21 16:06       ` Petri Rosenström
2010-12-23 14:44   ` Peter Humphrey
2010-12-23 15:54     ` Peter Humphrey
2011-04-01 11:43   ` Peter Humphrey
2011-04-02  8:57     ` Neil Bothwick
2011-04-02  9:15       ` Dale
2011-04-02 15:16       ` Peter Humphrey
2011-04-02 15:19   ` Peter Humphrey
2011-04-02 22:47     ` Neil Bothwick
2011-04-03 13:55       ` Peter Humphrey [this message]
2011-04-03 17:08         ` Neil Bothwick
2011-04-03 17:24           ` Peter Humphrey
2011-04-03 22:27             ` Peter Humphrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201104031455.39722.peter@humphrey.ukfsn.org \
    --to=peter@humphrey.ukfsn.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox