-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 15/11/12 03:43 PM, Duncan wrote: > Thomas Sachau posted on Thu, 15 Nov 2012 20:45:16 +0100 as > excerpted: > >> Ben de Groot schrieb: >>> On 14 November 2012 05:13, Thomas Sachau <to...@gentoo.org> >>> wrote: >>> >>>> Alexis Ballier schrieb: >>>>> - considering gentoo generally uses e-prefixed names >>>>> (econf, emake, etc.) maybe its wiser to name the variables >>>>> E17_* instead of only E_*, or ENLIGHTENMENT_*, so that it >>>>> makes the "confusion" harder. >>>>> >>>> Those functions are internal ebuild functions, while the >>>> USE_EXPANDed var is exposed to and may be used by the user, >>>> so i dont see a high risk of people mixing them. Maybe some >>>> other people can also comment on this? >>> >>> I agree that E_* is more confusing than it needs to be. Please >>> use something that is unmistakeably clearer. >>> >> ok, so what about ENLIGHTENMENT_MODULES as USE_EXPANDED var? > > That's certainly clear enough. Alternatively, something like ENL_* > would be shorter if somewhat more cryptic, but should eliminate any > possible E_* confusion. > > Because as a user I recently noted some package with a use-expand > that gets REALLY long in portage's emerge --verbose --pretend > output, which lists ALL variants on or off, with the prefix > repeated for each one. ENLIGHTENMENT_MODULES is certainly clear > enough, but when it's repeated a dozen or more times, once for each > expansion, that's a VERY long emerge --pretend --verbose output! >
Portage doesn't do this (for me at least, 2.1.11.31 and previous); it shows [USE_EXPAND]="possible1 possible2 possible3 ..."; no [use_expand_] prefixed on -v output .. Now, for dev's that might need to REQUIRED_USE it, yeah, we have to deal with that. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlClWecACgkQ2ugaI38ACPDl0wD/dxRXh+9/LnbYNRwebBK2upvY RWr4BIgKwIokNvJ4QnQA/1XgcOq6G2KkLSP1kL1zDQZBOD1wDBBACedhQVFqZCtR =bHMB -----END PGP SIGNATURE-----
