1 |
On 17/12/18 15:44, M. J. Everitt wrote: |
2 |
> On 17/12/18 12:54, Michał Górny wrote: |
3 |
>>> Not only this, but as noted, unless you know the man pages for portage and |
4 |
>>> make.conf in order to recite them in your sleep, they are confusing for |
5 |
>>> users, as they do not necessarily follow an obvious pattern, and it wasn't |
6 |
>>> until I was attempting to debug something that I noticed that despite |
7 |
>>> believing I had the correct settings in my make.conf (set over a period of |
8 |
>>> YEARS) they were in fact completely useless, and it wasn't until I had to |
9 |
>>> spend time with somebody debugging WTF was happening, that this particular |
10 |
>>> issue even became apparent... |
11 |
>> I don't see how this is an argument for anything. You have to read |
12 |
>> the manual in order to know that such variable exists and what it does. |
13 |
>> Or, well, technically you don't since it's provided in make.conf.example |
14 |
>> already where you only need to uncomment it. |
15 |
>> |
16 |
>> Either way, the variable name is trivial. Even if you don't follow |
17 |
>> the usual pattern of uncommenting it from make.conf.example or copying |
18 |
>> from the manual, remembering it for the time needed to retype shoudln't |
19 |
>> be a problem. |
20 |
>> |
21 |
>> So, is this a solution to a real problem? Or is it merely a half- |
22 |
>> thought-out partial change that's going to require people to update |
23 |
>> their configuration for no long-term benefit? And then they will have |
24 |
>> to update it again when someone decides to take another variable for |
25 |
>> a spin. |
26 |
>> |
27 |
> In the case you hadn't noticed, clearly you haven't .. the change is |
28 |
> backwards compatible.. that has already been thought out. |
29 |
> |
30 |
> But you haven't actually looked at the patch have you, Michal ? |
31 |
> |
32 |
Whilst I'm here .. you won't also have noticed I've updated the |
33 |
documentation too ... |