| 1 |
Mike Frysinger wrote: |
| 2 |
> On Thursday 01 February 2007, Daniel Black wrote: |
| 3 |
>> So some foo that says: |
| 4 |
>> die "you have enabled X USE flag but your saved config reflects the X USE |
| 5 |
>> flag been unset. Please correct your saved config by setting GUI=yes |
| 6 |
>> in /etc/portage/savedconfig/${CATEGORY}/${PXXX}/config.h or unset the USE |
| 7 |
>> flag X." |
| 8 |
> |
| 9 |
> problem i have with this is that you have to enumerate what could be a ton of |
| 10 |
> options and bind them to the appropriate USE flag |
| 11 |
> |
| 12 |
> easier to just say "USE=savedconfig overrides everything else" |
| 13 |
> -mike |
| 14 |
|
| 15 |
But at that point the manager has little or no control over the package, |
| 16 |
hell you can move the savedconfigs out of /etc/portage/ cause they have |
| 17 |
nothing to do with it at all. |
| 18 |
|
| 19 |
You can't do use-deps with this, because you can't effectively enumerate |
| 20 |
what a savedconfig build will actually build with (assumining |
| 21 |
savedconfig is enabled for that package) since the manager's choices |
| 22 |
will just get over-ridden. The PM would be required to essentially scan |
| 23 |
the savedconfig and parse them into an internal package config state. |
| 24 |
And from a PM point of view that blows ;) |
| 25 |
-- |
| 26 |
gentoo-dev@g.o mailing list |
Archives