Brian Harring wrote: > On Mon, Feb 13, 2006 at 11:23:26PM +0000, Alec Warner wrote: > >>Soo apparently I wasn't subscribed...stupid address changes ;) >> >>Patch ( which is actually v0.2 since 0.1 was a proof of concept.. ) for >>having USE flag defaults in ebuilds. The variable IUSE_DEFAULTS was >>chosen for backwards compatability, although I'm sure we will get >>complaints about extra variables and tree bloat. If you have a better >>variable name, by all means propose it ;) > > > IUSE- eapi bump it, I pushed for the var for exactly crap like this ;) > > The only (imo) reason to add the USE_ORDER chunks is because users use > -* to castrate auto-use; auto-use is dead in 2.1, so the main reason > for using -* is gone. > > So... really worth adding another chunk of metadata for this? >
Well that problem would be, no one wants to modify everything in app-portage/ :). If my portage EAPI is 1, but my tools don't support processing +- in IUSE, how does EAPI help me here? The support check is only for portage_const, so the tool remains fucked. Unless I'm missing something. > Tiz your guys show, your choice on it but either way, an EAPI bump > *should* be required (addition of new metadata that affects the > resultant/desired deps would qualify), so you've got room to manuever > on it. > > ~harring
signature.asc
Description: OpenPGP digital signature
