1 |
On Thu, Aug 18, 2005 at 01:16:05PM -0400, Alec Warner wrote: |
2 |
> As long as there is a way provided disable the 'default use flags' in |
3 |
> this case referring to the IUSE="+foo" stuff, with a big warning that |
4 |
> says crap generally isn't expected to work great with that setting on, |
5 |
> then thats fine. I can see something like a profile setting for this, |
6 |
> since embedded may not want the same IUSE defaults as AMD64 |
7 |
> multilib...this also saves the profiles from becoming huge with "Hi turn |
8 |
> this default flag off, and that flag off, and this flag on..." crud. |
9 |
See... -* shouldn't affect default IUSE. Why? Because if you make it |
10 |
flip off the ebuilds default use flags, you're forcing the ebuild to |
11 |
start using no* flags instead. Ebuilds are unconfigured- there are |
12 |
default IUSE serves purely as a way for the ebuild maintainer to allow |
13 |
the ebuild to be broken down further- they can do it now, by adding a |
14 |
crapload of no* flags. |
15 |
|
16 |
Allowing -* to castrate default IUSE forces them back into no* flags. |
17 |
|
18 |
Literally, for the embedded example, they already probably have all of |
19 |
the no* flags flipped on if needed- an action was taken, you just |
20 |
change it so it's USE="-theflag" rather then USE="noflag". Either |
21 |
way, the work involved is effectively the same. Either way, profiles |
22 |
shouldn't be screwing with the ebuilds in that fashion imo. |
23 |
|
24 |
Note this assuming this feature isn't used as a way to do 'suggested |
25 |
deps', where you start flipping on by default a lot of functionality |
26 |
the user didn't explicitly request (ala autouse). A default of +perl |
27 |
on mysql I'd view as wrong, for example. |
28 |
~harring |