From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] colon separated variables in /etc/env.d/
Date: Wed, 13 Sep 2006 22:45:16 -0400 [thread overview]
Message-ID: <200609132245.17506.vapier@gentoo.org> (raw)
In-Reply-To: <4504BF77.2020502@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 453 bytes --]
On Sunday 10 September 2006 21:44, Zac Medico wrote:
> For example, we can have a list of variable names
> stored in a new variable called "COLON_SEPARATED" that will reside
> in either the profiles or /etc/env.d/ itself.
/etc/env.d makes most sense ... we just have to worry about how to handle the
chicken & egg problem ...
so if you have FOO="..." in '10file' but COLON_SEPARATED="foo" doesn't appear
until '20file', what then ?
-mike
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2006-09-14 3:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 1:44 [gentoo-dev] colon separated variables in /etc/env.d/ Zac Medico
2006-09-11 3:36 ` Drake Wyrm
2006-09-11 7:17 ` Simon Stelling
2006-09-11 10:56 ` Danny van Dyk
2006-09-11 15:48 ` Zac Medico
2006-09-11 16:30 ` Donnie Berkholz
2006-09-11 17:42 ` Zac Medico
2006-09-11 16:51 ` Ciaran McCreesh
2006-09-11 17:57 ` Zac Medico
2006-09-11 20:02 ` Paul de Vrieze
2006-09-11 21:41 ` Zac Medico
2006-09-14 2:45 ` Mike Frysinger [this message]
2006-09-14 3:19 ` Zac Medico
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=200609132245.17506.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-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