-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Jul 09, 2007 at 11:26:19PM +0100, Ciaran McCreesh wrote: > As for IUSE defaults... There were objections against that feature on > the grounds that it's unnecessary and increased maintenance. Do they > really offer any benefit over package.use?
Would iuse defaults not be appropriate when a certain use flag is recommended as the default for most users for a package?? Here is an example, I think, where an iuse default would make sense. Espeak uses the portaudio library as a way to actually play sounds. However, it can also be compiled without portaudio in order to just generate wav files. The way espeak is currently in the tree, it requires portaudio, and that is the way I figure most people would want it to compile. The issue though is that the way we have it right now it is not possible to build espeak only to create wav files. There would be 2 ways I can see to do that. 1) Use the portaudio use flag, and put it in IUSE as +portaudio so that a user can turn it off if they desire, or 2) use a use flag something like "noportaudio", which would turn it off if the user enables it, but I don't like that because of the reverse logic -- If a flag is in use, it should enable support for something, not disable it. Is there another option that I'm missing, or is something like this a good case for iuse defaults? - -- William Hubbs gentoo accessibility team lead [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFGkxHwblQW9DDEZTgRAirDAJ4y50ul/NbtMM+nyTHH7y7Y7N3NdQCeMVEW 8rY3UNew30RgEFqW42sMwzE= =Um4Q -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
