From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] [PATCH 2/2] modules/generic_stage_target.py, modules/stage1_target.py: Add a target_mounts dictionary
Date: Wed, 18 Dec 2013 23:34:36 -0800 [thread overview]
Message-ID: <1387438476.3897.222.camel@big_daddy.dol-sen.ca> (raw)
In-Reply-To: <20131218053547.GL25409@odin.tremily.us>
[-- Attachment #1: Type: text/plain, Size: 1677 bytes --]
On Tue, 2013-12-17 at 21:35 -0800, W. Trevor King wrote:
> On Tue, Dec 17, 2013 at 09:18:04PM -0800, Brian Dolbec wrote:
> > On Tue, 2013-12-17 at 19:28 -0800, W. Trevor King wrote:
> > > On Tue, Dec 17, 2013 at 05:07:27PM -0800, Brian Dolbec wrote:
> > > > - self.mounts.append("/var/log/portage")
> > > > - self.mountmap["/var/log/portage"]=self.settings["port_logdir"]
> > > > - self.env["PORT_LOGDIR"]="/var/log/portage"
> > > > + self.mounts.append("port_logdir")
> > > > + self.mountmap["port_logdir"]=self.settings["port_logdir"]
> > > > + self.env["PORT_LOGDIR"]=self.settings["port_logdir"]
> > >
> > > I also think that the PORT_LOGDIR environment variable
> > > should be:
> > >
> > > self.env["PORT_LOGDIR"] = self.target_mounts["port_logdir"]
> I don't care about caps, I was trying to fix settings → target_mounts,
> since settings holds the mount source ;).
>
> Cheers,
> Trevor
>
No, this code block is adding it to the environment if defined in
settings. This patch was just removing the hard coded paths.
This is the full if block:
if "port_logdir" in self.settings:
self.mounts.append("port_logdir")
self.mountmap["port_logdir"]=self.settings["port_logdir"]
self.env["PORT_LOGDIR"]=self.settings["port_logdir"]
self.env["PORT_LOGDIR_CLEAN"]='find "${PORT_LOGDIR}" -type f ! -name "summary.log*" -mtime +30 -delete'
So far it is not used from the new TARGET_MOUNTS_DEFAULTS.
It is so far only enabled if uncommented and defined in catalyst.conf or
from the cli.
Should I remove it from the TARGET_MOUNTS_DEFAULTS for the time being?
--
Brian Dolbec <dolsen@gentoo.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
next prev parent reply other threads:[~2013-12-19 7:34 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
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 [this message]
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=1387438476.3897.222.camel@big_daddy.dol-sen.ca \
--to=dolsen@gentoo.org \
--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