From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Re: [PATCH] man pages: note that make.conf can be a directory (463266)
Date: Mon, 29 Dec 2014 02:55:24 +0000 (UTC) [thread overview]
Message-ID: <pan$2fbf0$d8aafedb$41b5e232$3681825e@cox.net> (raw)
In-Reply-To: 549E573A.3090104@gentoo.org
Zac Medico posted on Fri, 26 Dec 2014 22:52:42 -0800 as excerpted:
>> I believe that's why I chose to stick with a make.conf file that simply
>> sourced a bunch of other files, instead of simply making it a directory
>> and sticking all those other files in the dir, when I first read about
>> the possibility. I have scripts myself that simply source make.conf,
>> that I'd have to rewrite with a for loop to process a directory. It's
>> not hard to do, but people haven't had to worry about it and so they
>> haven't. If people aren't thinking about that when they up and make
>> make.conf a directory, they might well wish they had! =8^0
>
> Why don't you use 'portageq envvar'?
Thanks for the hint. I will likely use it. =:^)
Which hints at half the answer to your question; I didn't really know
about it. The other half of the answer is simple. It was never needed
before, as sourcing make.conf always "just worked". Now that it's
needed... Thanks again! =:^)
--
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:[~2014-12-29 2:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 22:01 [gentoo-portage-dev] [PATCH] man pages: note that make.conf can be a directory (463266) Zac Medico
2014-12-27 6:22 ` [gentoo-portage-dev] " Duncan
2014-12-27 6:52 ` Zac Medico
2014-12-29 2:55 ` Duncan [this message]
2014-12-29 3:01 ` Zac Medico
2015-01-05 13:12 ` [gentoo-portage-dev] " Alexander Berntsen
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$2fbf0$d8aafedb$41b5e232$3681825e@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