- I think sometimes we want to update world or all packages to use new USE flag. emerge should have some options like these to update currently emerged package to use new USE flag. emerge --update --update-use And with all package in dependencies. emerge --update --empytree --update-use I mean. To update current installed package to satisfy new USE flag. For example. If we have xfree installed with '-3dfx' use flag. After we change to use '3dfx' flag and rerun emerge --update --update-use. xfree and other packages that have 3dfx use flag need to emerge to satisfy new use flag. emerge --update-use [ebuild R ] x11-base/xfree-4.2.1-r2 *sse *nls *mmx *truetype _3dnow +3dfx - May be this enhancement related to Bug #3252. USE flag shold use old USE flag when update. I think this --update-use option is more suitable when we want to update to new USE flag. - And more. emerge should show some of use flags to be change on pretend option. For example. I have add new '3dnow' and remove 'mmx' of use flag and emerge xfree. emerge xfree --pretend --verbose --update-use [ebuild R ] x11-base/xfree-4.2.1-r2 *sse *nls -mmx *truetype +3dnow _3dfx If we don't use --update-use. It should be like these. emerge xfree --pretend --verbose [ebuild R ] x11-base/xfree-4.2.1-r2 *sse *nls *mmx *truetype _3dnow _3dfx Some symbol indicates change on use flag. * use flag that already use _ use flag that already not use + use flag to add - use flag to remove
I've written a preliminary program to do this: Information + Screenshot: http://forums.gentoo.org/viewtopic.php?t=50078 Script: http://www.coe.uncc.edu/~danderse/www/usechange
*** Bug 19616 has been marked as a duplicate of this bug. ***
*** Bug 29719 has been marked as a duplicate of this bug. ***
*** Bug 39680 has been marked as a duplicate of this bug. ***
This feature request may be necessary, to avoid a problem with USE flags that change, as described in bug 39680. I shall continue discussing the problem there, as it is not relevant to this feature request, except as a motivating factor. This feature request, however, is relevant to the bug, as a possible solution.
--newuse in 2.0.51
Another information should be added like to use etc-update, I think ... * Your USE flags has been changed [and some more instruction to use --newuse]
Bug has been fixed and released in stable portages on or before 2.0.51-r2