So,
a support for specific USE flags description could be
implemented directly in the ebuild file. The
description would not be required. But when it is
beyond 'enabling or disabling support for foo' the
contributor is encourged to do it.
I believe that in the future use.desc will have no
use, mainly because all description will be available
in the ebuild file.
But I'm concerned about the --newuse stuff. Lots of
new flags can make it obscure, disabling or enabling
sets of undesired functionality 'in loco' (it actually
happens nowadays).
What to do about it? It's possible to use USE flags
only for support of characteristics and create another
set of Specific USE flags - 'SUSE' :) ?
=====
Atenciosamente
Romeu Henrique Capparelli Fonseca
Sistemas Software Livre
tel: (11) 81397109
mail: [EMAIL PROTECTED]
mail: [EMAIL PROTECTED]
_______________________________________________________
Yahoo! Acesso Gr�tis - Instale o discador do Yahoo! agora.
http://br.acesso.yahoo.com/ - Internet r�pida e gr�tis
--
[email protected] mailing list
