-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jason Stubbs wrote:
| What are the exact reasons for not wanting to put the expanded flags
directly
| into IUSE? If it's just a matter of the horrid display existing tools
would
| give, the functionality can go in and IUSE updated after the functional
| versions are stabled. Are there any reasons beyond that?
It's useful to group things logically like this. You don't need to worry
about forgetting to add in variables like:
IUSE_VIDEO_CARDS="foo bar"
IUSE="${IUSE_VIDEO_CARDS} baz bop"
Particularly when you start doing things in eclasses as well as ebuilds,
this gets worrisome. It's also more aesthetically pleasing. And it
creates a logical parallel with the user-set variables in make.conf.
In addition, it saves IUSE from having super-long flags:
IUSE="video_cards_foo video_cards_bar video_cards_baz ... " -- picture
that repeated 10 times. It's just plain ugly and overly long.
Most importantly IMHO, it suggests that users should set
USE="video_cards_foo" instead of VIDEO_CARDS="foo".
Thanks,
Donnie
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDOhnaXVaO67S1rtsRAvT2AJoDRphFhWJaPc1G0OuISixe1jE9AgCeIZnQ
YS1fBH92GQOG6tDreeP93sw=
=XK5J
-----END PGP SIGNATURE-----
--
[email protected] mailing list
