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