| 1 |
Stuart Herbert wrote: |
| 2 |
> |
| 3 |
> I can see where you're coming from, but I'm not sure it's worth the |
| 4 |
> potential disruption that this will cause our users. |
| 5 |
> |
| 6 |
> Unless I'm missing something, won't every user who has any form of |
| 7 |
> USE=xml, USE=-xml, USE=xml2, or USE=-xml2 in make.conf and packages.use |
| 8 |
> get a nasty surprise the next time they emerge -u world? |
| 9 |
> |
| 10 |
> I haven't seen any discussion taking this into account yet. |
| 11 |
> |
| 12 |
> Best regards, |
| 13 |
> Stu |
| 14 |
|
| 15 |
Most profiles turn on xml2 by default so we can just have the xml global |
| 16 |
use flag on by default to avoid most breakage. Then people turning -xml2 |
| 17 |
will just get xml until they switch to -xml. If you want to run a |
| 18 |
minimal ship, you should be doing emerge -pv any way before updates to |
| 19 |
check for new use flags. |
| 20 |
|
| 21 |
betelgeuse@pena /usr/portage/profiles $ grep xml2 -r |
| 22 |
/usr/portage/profiles/ -l |
| 23 |
|
| 24 |
package.use is probably something we can't affect atm. It would probably |
| 25 |
be useful if Portage checked for unexisting flags in it. This is just |
| 26 |
one of those things that have to be properly informated to the user base |
| 27 |
until our tools are better in handling these situations. |
| 28 |
|
| 29 |
Regards, |
| 30 |
Petteri |
Archives