| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Am 03.12.2013 17:05, schrieb Mike Frysinger: |
| 5 |
> as for the patch, i'm of the opinion that make.conf is not for |
| 6 |
> documenting random USE_EXPAND-ed variables. |
| 7 |
> |
| 8 |
> this sort of thing should go into the relevant eclass, |
| 9 |
> python-r1.eclass in this case. then people would read about it via |
| 10 |
> `man python-r1.eclass`. |
| 11 |
|
| 12 |
I object. As a user you should (most of the time) not need to read |
| 13 |
eclass-documentation. And even if you'd count this as a necessity: How |
| 14 |
should a user know _which_ eclass documentation to read? I think such |
| 15 |
a thing is way too much 'implementation detail'. |
| 16 |
|
| 17 |
If you all think, that make.conf.5 is not the right place (which I |
| 18 |
understand), then there should be another central place where the most |
| 19 |
important USE_EXPAND-ed vars are explained and/or pointers provided. |
| 20 |
Perhaps one could make (active) contribution to this place a |
| 21 |
prerequisite to obtaining a new USE_EXPAND-var. |
| 22 |
|
| 23 |
And in make.conf.5 there then can be a pointer to this central |
| 24 |
documentation. |
| 25 |
|
| 26 |
- - René |
| 27 |
-----BEGIN PGP SIGNATURE----- |
| 28 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 29 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 30 |
|
| 31 |
iQEcBAEBAgAGBQJSnhcNAAoJEC/VbLI/MjXALUEH/iloA1/Pxee/0K3dv3s3P0NO |
| 32 |
buDmWKLQQ/rtUwlaM3VZj4b71MqHK7zIjumD+9IIq9to4l/ot5Bsx8hUbdcyJtsa |
| 33 |
wrSPZBKGeYw9m3qYmP9GIr9uKb+/BfUPrfGefSp3rtWPnaAb1clZJbC40Hw+J2Mp |
| 34 |
rzKWzvmweqVbrzXSg/Dm38+JqBozQFk1cbHshe2d15S/Cem4yCn+NQaPSl7l1hQE |
| 35 |
eljJ/b5lGbIeF8QxtPJPwSVEv/ohC6nXLK7eKvGDXvV0ZpuDl9KvmeYpc8/40d9n |
| 36 |
LSzTBB7ENEC34hpTwhoTekufitmFj/IRvN63ekHf6+asjrfhCejFCO6HKZFa3I4= |
| 37 |
=Rky6 |
| 38 |
-----END PGP SIGNATURE----- |
Archives