Summary: | emerge --newuse - re-emerge triggered on USE_EXPAND_HIDDEN stuff changes without any visible reason | ||
---|---|---|---|
Product: | Portage Development | Reporter: | trefoil <gentoo> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jakub |
Priority: | High | Keywords: | InVCS |
Version: | 2.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 181949 | ||
Attachments: | portage-2.1.3_rc8 patch to prevent flags from being hidden when appropriate |
Description
trefoil
2007-07-11 18:47:57 UTC
*** This bug has been marked as a duplicate of bug 161980 *** Reopen. As noted on the other bug - find a solution that doesn't confuse the hell out of users, I think I'll fix the USE_EXPAND_HIDDEN hidden code so that these flags aren't hidden when a package is being reinstalled due to one of these flags. I'd still say that re-emerging packages on this kind of IUSE changes is not useful, but the above solution is still much better than the current state of things. :) FWIW, the current workaround to see the flags is this: USE_EXPAND_HIDDEN="-*" emerge <args> Created attachment 124602 [details, diff]
portage-2.1.3_rc8 patch to prevent flags from being hidden when appropriate
This is fixed in svn r7238.
Thank you both for your help. Portage is the one of the few areas of Gentoo where I feel like I'm being treated with respect wrt bug reports. :) This has been released in 2.1.3_rc9. |