1 |
On 12/26/2014 10:22 PM, Duncan wrote: |
2 |
> Zac Medico posted on Fri, 26 Dec 2014 14:01:47 -0800 as excerpted: |
3 |
> |
4 |
>> Commit 86e75790954e766beba75443d967b2c25055c5b0 added support for |
5 |
>> make.conf to be a directory, but the feature was undocumented. |
6 |
>> Therefore, update the man pages, as suggested in bug #465164, comment |
7 |
>> #9. |
8 |
> |
9 |
> What about other apps that parse make.conf? A note that this might break |
10 |
> compatibility with some of them, and/or with other scripts people |
11 |
> sometimes post on the forums, lists, etc, could be worthwhile. |
12 |
|
13 |
I think this goes without saying. External tools would really be better |
14 |
off calling 'portageq envvar' than parsing make.conf directly. I think |
15 |
it's fine to let people discover such issues themselves, and report bugs |
16 |
for the corresponding tools. Maybe that will help generate some noise |
17 |
that will give the maintainers some incentive to fix those tools. |
18 |
|
19 |
Cluttering our documentation with compatibility notes that will |
20 |
eventually become outdated seems kind of pointless. Also, such notes are |
21 |
not necessarily relevant to all users, so that's another reason I would |
22 |
prefer to omit them. |
23 |
|
24 |
> I believe that's why I chose to stick with a make.conf file that simply |
25 |
> sourced a bunch of other files, instead of simply making it a directory |
26 |
> and sticking all those other files in the dir, when I first read about |
27 |
> the possibility. I have scripts myself that simply source make.conf, |
28 |
> that I'd have to rewrite with a for loop to process a directory. It's |
29 |
> not hard to do, but people haven't had to worry about it and so they |
30 |
> haven't. If people aren't thinking about that when they up and make |
31 |
> make.conf a directory, they might well wish they had! =8^0 |
32 |
|
33 |
Why don't you use 'portageq envvar'? |
34 |
|
35 |
> Most of the others I've made dirs, tho. It's much easier configuring |
36 |
> portage that way, and as I said, my make.conf is already just a bunch of |
37 |
> source directives, giving me pretty much the best of both worlds. =:^) |
38 |
> |
39 |
> (Until I add a new configuration file and forget to add a corresponding |
40 |
> source line for it in make.conf, as I did recently. =:^( ) |
41 |
> |
42 |
> I'll eventually do make.conf as well, but it's not worth worrying about |
43 |
> changing my scripts until all the packages that reference it are known to |
44 |
> handle it. |
45 |
|
46 |
These bug reports for euse, euses, and ufed come to mind: |
47 |
|
48 |
https://bugs.gentoo.org/show_bug.cgi?id=474574 |
49 |
https://bugs.gentoo.org/show_bug.cgi?id=478318 |
50 |
|
51 |
If I actually used any of those tools, then they probably would have |
52 |
been fixed long ago. |
53 |
-- |
54 |
Thanks, |
55 |
Zac |