public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: "W. Trevor King" <wking@tremily.us>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] [PATCH 1/2] modules/generic_stage_target.py: USE portdir, distdir,... instead of paths for keys
Date: Tue, 17 Dec 2013 19:30:49 -0800	[thread overview]
Message-ID: <20131218033048.GE25409@odin.tremily.us> (raw)
In-Reply-To: <1387336507.3897.180.camel@big_daddy.dol-sen.ca>

[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]

On Tue, Dec 17, 2013 at 07:15:07PM -0800, Brian Dolbec wrote:
> On Tue, 2013-12-17 at 19:10 -0800, W. Trevor King wrote:
> > On Tue, Dec 17, 2013 at 05:07:26PM -0800, Brian Dolbec wrote:
> > >  		if "SNAPCACHE" in self.settings:
> > > -			self.mounts=["/proc","/dev","/usr/portage","/usr/portage/distfiles","/var/tmp/portage"]
> > > -			self.mountmap={"/proc":"/proc","/dev":"/dev","devpts":"/dev/pts",
> > > -				"/usr/portage":self.settings["snapshot_cache_path"]+"/portage",\
> > > -				"/usr/portage/distfiles":self.settings["distdir"],"/var/tmp/portage":"tmpfs"}
> > > +			self.mounts=["proc", "dev", "portdir", "distdir", "port_tmpdir"]
> > > +			self.mountmap={"proc":"/proc", "dev":"/dev", "devpts":"/dev/pts",
> > > +				"portdir":self.settings["snapshot_cache_path"]+"/portage",\
> > > +				"distdir":self.settings["distdir"],"port_tmpdir":"tmpfs"}
> > >  		else:
> > >  			self.mounts = ["proc", "dev", "distdir", "port_tmpdir"]
> > >  			self.mountmap = {"proc":"/proc", "dev":"/dev", "devpts":"/dev/pts",
> > 
> > Where does /usr/portage come from if SNAPCACHE is not enabled?  Is it
> > just bind-mounted from the host's /usr/portage?
> 
> It comes from the snapshot tarball created during a snapshot run.
> SnapCache just keeps an unpacked copy ready to reuse.  That way it can
> skip the unpack stage.

In that case, this patch is acked-by me.

Cheers,
Trevor

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-12-18  3:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18  1:07 [gentoo-catalyst] Mounts and Mountmap completions, fixes. Try 2: Brian Dolbec
2013-12-18  1:07 ` [gentoo-catalyst] [PATCH 1/2] modules/generic_stage_target.py: USE portdir, distdir,... instead of paths for keys Brian Dolbec
2013-12-18  3:10   ` W. Trevor King
2013-12-18  3:15     ` Brian Dolbec
2013-12-18  3:30       ` W. Trevor King [this message]
2013-12-18  1:07 ` [gentoo-catalyst] [PATCH 2/2] modules/generic_stage_target.py, modules/stage1_target.py: Add a target_mounts dictionary Brian Dolbec
2013-12-18  3:28   ` W. Trevor King
2013-12-18  5:18     ` Brian Dolbec
2013-12-18  5:35       ` W. Trevor King
2013-12-19  7:34         ` Brian Dolbec
2013-12-19  7:47           ` Brian Dolbec
2013-12-19 17:20             ` W. Trevor King

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=20131218033048.GE25409@odin.tremily.us \
    --to=wking@tremily.us \
    --cc=gentoo-catalyst@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