| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Mon, Jul 09, 2007 at 11:26:19PM +0100, Ciaran McCreesh wrote: |
| 5 |
> As for IUSE defaults... There were objections against that feature on |
| 6 |
> the grounds that it's unnecessary and increased maintenance. Do they |
| 7 |
> really offer any benefit over package.use? |
| 8 |
|
| 9 |
|
| 10 |
Would iuse defaults not be appropriate when a certain use flag is |
| 11 |
recommended as the default for most users for a package?? |
| 12 |
|
| 13 |
Here is an example, I think, where an iuse default would make sense. |
| 14 |
Espeak uses the portaudio library as a way to actually play sounds. |
| 15 |
However, it can also be compiled without portaudio in order to just |
| 16 |
generate wav files. |
| 17 |
|
| 18 |
The way espeak is currently in the tree, it requires portaudio, and that |
| 19 |
is the way I figure most people would want it to compile. |
| 20 |
|
| 21 |
The issue though is that the way we have it right now it is not possible |
| 22 |
to build espeak only to create wav files. There would be 2 ways I can |
| 23 |
see to do that. |
| 24 |
|
| 25 |
1) Use the portaudio use flag, and put it in IUSE as +portaudio so that |
| 26 |
a user can turn it off if they desire, or |
| 27 |
2) use a use flag something like "noportaudio", which would turn it off |
| 28 |
if the user enables it, but I don't like that because of the reverse |
| 29 |
logic -- If a flag is in use, it should enable support for something, |
| 30 |
not disable it. |
| 31 |
|
| 32 |
Is there another option that I'm missing, or is something like this a |
| 33 |
good case for iuse defaults? |
| 34 |
|
| 35 |
- -- |
| 36 |
William Hubbs |
| 37 |
gentoo accessibility team lead |
| 38 |
williamh@g.o |
| 39 |
-----BEGIN PGP SIGNATURE----- |
| 40 |
Version: GnuPG v1.4.7 (GNU/Linux) |
| 41 |
|
| 42 |
iD8DBQFGkxHwblQW9DDEZTgRAirDAJ4y50ul/NbtMM+nyTHH7y7Y7N3NdQCeMVEW |
| 43 |
8rY3UNew30RgEFqW42sMwzE= |
| 44 |
=Um4Q |
| 45 |
-----END PGP SIGNATURE----- |
| 46 |
-- |
| 47 |
gentoo-dev@g.o mailing list |
Archives