| 1 |
On Tue, 2013-12-03 at 18:38 +0100, René Neumann wrote: |
| 2 |
> Am 03.12.2013 17:05, schrieb Mike Frysinger: |
| 3 |
> > as for the patch, i'm of the opinion that make.conf is not for |
| 4 |
> > documenting random USE_EXPAND-ed variables. |
| 5 |
> > |
| 6 |
> > this sort of thing should go into the relevant eclass, |
| 7 |
> > python-r1.eclass in this case. then people would read about it via |
| 8 |
> > `man python-r1.eclass`. |
| 9 |
> |
| 10 |
> I object. As a user you should (most of the time) not need to read |
| 11 |
> eclass-documentation. And even if you'd count this as a necessity: How |
| 12 |
> should a user know _which_ eclass documentation to read? I think such |
| 13 |
> a thing is way too much 'implementation detail'. |
| 14 |
> |
| 15 |
> If you all think, that make.conf.5 is not the right place (which I |
| 16 |
> understand), then there should be another central place where the most |
| 17 |
> important USE_EXPAND-ed vars are explained and/or pointers provided. |
| 18 |
> Perhaps one could make (active) contribution to this place a |
| 19 |
> prerequisite to obtaining a new USE_EXPAND-var. |
| 20 |
> |
| 21 |
> And in make.conf.5 there then can be a pointer to this central |
| 22 |
> documentation. |
| 23 |
> |
| 24 |
> - René |
| 25 |
|
| 26 |
+1 |
| 27 |
|
| 28 |
It follows similarly with what I proposed about having a generic USE |
| 29 |
EXPAND heading and description in make.conf. It just doesn't show the |
| 30 |
python_targets as an example. but it could still, just not with the |
| 31 |
extra documentation that Alexander did. Instead point to this landing |
| 32 |
page for all the use expand variables. |
Archives