| 1 |
Zac Medico posted on Fri, 26 Dec 2014 22:52:42 -0800 as excerpted: |
| 2 |
|
| 3 |
>> I believe that's why I chose to stick with a make.conf file that simply |
| 4 |
>> sourced a bunch of other files, instead of simply making it a directory |
| 5 |
>> and sticking all those other files in the dir, when I first read about |
| 6 |
>> the possibility. I have scripts myself that simply source make.conf, |
| 7 |
>> that I'd have to rewrite with a for loop to process a directory. It's |
| 8 |
>> not hard to do, but people haven't had to worry about it and so they |
| 9 |
>> haven't. If people aren't thinking about that when they up and make |
| 10 |
>> make.conf a directory, they might well wish they had! =8^0 |
| 11 |
> |
| 12 |
> Why don't you use 'portageq envvar'? |
| 13 |
|
| 14 |
Thanks for the hint. I will likely use it. =:^) |
| 15 |
|
| 16 |
Which hints at half the answer to your question; I didn't really know |
| 17 |
about it. The other half of the answer is simple. It was never needed |
| 18 |
before, as sourcing make.conf always "just worked". Now that it's |
| 19 |
needed... Thanks again! =:^) |
| 20 |
|
| 21 |
-- |
| 22 |
Duncan - List replies preferred. No HTML msgs. |
| 23 |
"Every nonfree program has a lord, a master -- |
| 24 |
and if you use the program, he is your master." Richard Stallman |
Archives