1 |
On Mon, Aug 07, 2006 at 10:01:12AM +0200, Jakub Moc wrote: |
2 |
> Zac Medico wrote: |
3 |
> > Donnie Berkholz wrote: |
4 |
> >>> agaffney suggested this in the first place, and every time I think about |
5 |
> >>> it, it seems like a better idea. If we set VIDEO_CARDS and INPUT_DEVICES |
6 |
> >>> in the arch profiles, we get the arch-specific defaults we need without |
7 |
> >>> the really hugely ugly indecipherable mess in the ebuilds that nobody |
8 |
> >>> can understand besides Josh_B and me. The very strange corner case this |
9 |
> >>> doesn't work with is if people manually set VIDEO_CARDS="", then they |
10 |
> >>> will no longer get the behavior of pulling in everything. But the |
11 |
> >>> default case will still work great. |
12 |
> > |
13 |
> > As of portage-2.1.1_pre4-r4, VIDEO_CARDS="" should now continue to work like |
14 |
> > before no matter how you've enabled the flags in the profile. |
15 |
> |
16 |
> > As part of the fix for bug 142125, portage automatically regenerates all of |
17 |
> > the USE_EXPAND variables to be consistent with the corresponding USE |
18 |
> flags. |
19 |
> > |
20 |
> > Zac |
21 |
> |
22 |
> Well, please don't change the behaviour in every other release, it's |
23 |
> very confusing and people file bugs about it. And -r4 behaviour is |
24 |
> incorrect, as it ignores defaults in profiles when you set anything in |
25 |
> make.conf. -r3 got it correctly so that foo in profiles could be |
26 |
> overriden with -foo in make.conf, this doesn't work any more in -r4. |
27 |
|
28 |
That was a bug, not a feature. Older portage versions behave as -r4 |
29 |
does, and -r3's behaviour forces users to set invalid values in |
30 |
certain cases. |
31 |
-- |
32 |
gentoo-dev@g.o mailing list |