[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-portage-dev
Subject:    Re: [gentoo-portage-dev] Re: [PATCH] man pages: note that make.conf can be a directory (463266)
From:       Zac Medico <zmedico () gentoo ! org>
Date:       2014-12-29 3:01:47
Message-ID: 54A0C41B.7020605 () gentoo ! org
[Download RAW message or body]

On 12/28/2014 06:55 PM, Duncan wrote:
> 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!  =:^)

Note that it's handy to pull multiple variables into your environment
with a single portageq call like this:

	eval "$(portage envvar -v VARIABLE_1 VARIABLE_2 ...)"

For example, we use this construct in emerge-webrsync.
-- 
Thanks,
Zac

[prev in list] [next in list] [prev in thread] [next in thread]