From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] iuse defaults example
Date: Mon, 9 Jul 2007 23:58:24 -0500 [thread overview]
Message-ID: <20070710045824.GA6673@linux1> (raw)
-----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
williamh@gentoo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFGkxHwblQW9DDEZTgRAirDAJ4y50ul/NbtMM+nyTHH7y7Y7N3NdQCeMVEW
8rY3UNew30RgEFqW42sMwzE=
=Um4Q
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2007-07-10 5:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 4:58 William Hubbs [this message]
2007-07-10 5:20 ` [gentoo-dev] iuse defaults example Mike Frysinger
2007-07-10 8:31 ` Petteri Räty
2007-07-10 9:04 ` Mike Frysinger
2007-07-10 16:12 ` Thilo Bangert
2007-07-10 19:44 ` Thomas de Grenier de Latour
2007-07-10 20:30 ` Mike Frysinger
2007-07-10 20:47 ` Thomas de Grenier de Latour
2007-07-10 21:32 ` Mike Frysinger
2007-07-15 9:53 ` Thomas de Grenier de Latour
2007-07-15 11:57 ` Marius Mauch
2007-07-15 12:53 ` Thomas de Grenier de Latour
2007-07-15 19:22 ` Mike Frysinger
2007-07-15 20:24 ` Arfrever Frehtes Taifersar Arahesis
2007-07-15 21:21 ` Mike Frysinger
2007-07-16 11:42 ` [gentoo-dev] " Steve Long
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070710045824.GA6673@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox