From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Re: @sets and @profile does not work when ROOT=PORTAGE_CONFIGROOT=/my/new/root
Date: Fri, 23 Oct 2015 05:03:56 +0000 (UTC) [thread overview]
Message-ID: <pan$c7c87$7da5db71$80abb0ad$5d9db8c8@cox.net> (raw)
In-Reply-To: 562930EF.1020500@gentoo.org
Zac Medico posted on Thu, 22 Oct 2015 11:54:39 -0700 as excerpted:
> On 10/22/2015 11:29 AM, Joakim Tjernlund wrote:
>> On Thu, 2015-10-22 at 08:54 -0700, Zac Medico wrote:
>>> For example, the default set configuration located at
>>> /usr/share/portage/config/sets/portage.conf does something similar
>>> with %(PORTAGE_CONFIGROOT)s.
>>
>> Nice! I am a bit puzzled over the trailing s in ..)s, is that a typo?
>> if not what does it mean?
>
> The trailing s is required. It's python configparser interpolation
> syntax:
>
> https://docs.python.org/3/library/configparser.html#interpolation-of-values
Thanks. That's a pattern I now recognize and identify elsewhere. =:^)
And that recognition/identification presumably answers a low-priority
(thus never asked) question I've had for some time about layman.conf, and
what/why it uses variable interpolation with the same trailing s, which I
hadn't understood until now.
For me, the answer is now essentially "the trailing 's' is an artifact of
the python implementation and its use of the configparser lib, and yes,
it's necessary, and doesn't mean the path now needs a literal trailing
's' as well."
Again, thanks. Seeing similar trailing-s usage should be way less
confusing now. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-10-23 5:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 16:47 [gentoo-portage-dev] @sets and @profile does not work when ROOT=PORTAGE_CONFIGROOT=/my/new/root Joakim Tjernlund
2015-10-22 4:35 ` Zac Medico
2015-10-22 7:05 ` Joakim Tjernlund
2015-10-22 15:54 ` Zac Medico
2015-10-22 18:29 ` Joakim Tjernlund
2015-10-22 18:54 ` Zac Medico
2015-10-22 19:16 ` Joakim Tjernlund
2015-10-22 19:25 ` Zac Medico
2015-10-22 20:54 ` Joakim Tjernlund
2015-10-22 21:08 ` Zac Medico
2015-10-23 5:03 ` Duncan [this message]
2015-10-23 9:21 ` Joakim Tjernlund
2015-10-24 20:49 ` Zac Medico
2015-10-23 1:36 ` [gentoo-portage-dev] [PATCH] RepoConfigLoader: allow subsitution of variables like ROOT in repos.conf Zac Medico
2015-10-28 13:28 ` Brian Dolbec
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='pan$c7c87$7da5db71$80abb0ad$5d9db8c8@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-portage-dev@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