| 1 |
Alexander Berntsen posted on Tue, 03 Dec 2013 11:43:42 +0100 as excerpted: |
| 2 |
|
| 3 |
> On 03/12/13 11:21, Sebastian Luther wrote: |
| 4 |
>> The problem with all these variables is that we don't maintain them. If |
| 5 |
>> they disappear, change meaning or new ones are added we constantly have |
| 6 |
>> to fix our documentation. |
| 7 |
> I don't think this is a problem. I could fix any documentation bugs |
| 8 |
> related to this. |
| 9 |
> |
| 10 |
>> The python team's documentation [1] is just fine imo. Maybe this one |
| 11 |
>> needs to be more user visible? Maybe by linking it into the handbook |
| 12 |
>> (if it isn't already)? |
| 13 |
> It could be linked in the man page of make.conf as well. |
| 14 |
> |
| 15 |
> |
| 16 |
> Ultimately my stance is that it should be in the man page. I can add |
| 17 |
> them myself. However, I will leave it out if more people agree with |
| 18 |
> Sebastian than me. |
| 19 |
|
| 20 |
User contribution, FWIW: I'll stay neutral on having it in the manpage, |
| 21 |
but I definitely agree PYTHON_TARGETS and PYTHON_SINGLE_TARGET need more |
| 22 |
visibility, and I like the proposed explanation in the patch very much, |
| 23 |
as it finally cleared up the relationship between the two of them for me. |
| 24 |
|
| 25 |
And given my level of gentoo knowledge and experience, if I was a bit |
| 26 |
confused by the two separate python-targets settings and unaware of the |
| 27 |
precise relationship between them as well as their defaults, I think it's |
| 28 |
a pretty safe bet that well above 90% of the user base is at least as |
| 29 |
confused as I was if not more so. So manpage or some other location I'm |
| 30 |
not sure, but I definitely agree it's not documented well enough now, and |
| 31 |
the proposed patch would at least give it /some/ visibility. |
| 32 |
|
| 33 |
Regardless of whether it gets in the manpage, tho, can I suggest |
| 34 |
mentioning that definition in the next GMN, gentoo monthly newsletter, |
| 35 |
now that it has been resurrected? The handbook and/or manpage are good, |
| 36 |
but that won't necessarily reach the existing users GMN should, even if |
| 37 |
it doesn't reach them all. From there the explanation will hopefully |
| 38 |
spread via the users themselves. =:^) |
| 39 |
|
| 40 |
-- |
| 41 |
Duncan - List replies preferred. No HTML msgs. |
| 42 |
"Every nonfree program has a lord, a master -- |
| 43 |
and if you use the program, he is your master." Richard Stallman |
Archives