| 1 |
On Tue, 2013-12-03 at 11:43 +0100, Alexander Berntsen wrote: |
| 2 |
> On 03/12/13 11:21, Sebastian Luther wrote: |
| 3 |
> > The problem with all these variables is that we don't maintain |
| 4 |
> > them. If they disappear, change meaning or new ones are added we |
| 5 |
> > constantly have to fix our documentation. |
| 6 |
> I don't think this is a problem. I could fix any documentation bugs |
| 7 |
> related to this. |
| 8 |
> |
| 9 |
> > The python team's documentation [1] is just fine imo. Maybe this |
| 10 |
> > one needs to be more user visible? Maybe by linking it into the |
| 11 |
> > handbook (if it isn't already)? |
| 12 |
> It could be linked in the man page of make.conf as well. |
| 13 |
> |
| 14 |
> |
| 15 |
> Ultimately my stance is that it should be in the man page. I can add |
| 16 |
> them myself. However, I will leave it out if more people agree with |
| 17 |
> Sebastian than me. |
| 18 |
|
| 19 |
I think a good compromise is to use python_targets as an example under a |
| 20 |
general use expand heading, explaining how use expand works. Add the |
| 21 |
link to the python doc, yes |
| 22 |
|
| 23 |
Then simply mention to look for the relevant docs for details of any of |
| 24 |
the other use expand variables. And a pointer to the gentoo docs index. |
| 25 |
|
| 26 |
I think python_targets is too central to a gentoo system to be |
| 27 |
completely ignored in the man pages. |
Archives