Summary: | emerge --newuse forces rebuild when use flag is removed | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Caleb Cushing <xenoterracide> |
Component: | Core - Interface (emerge) | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | czarkoff |
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Caleb Cushing
2006-11-28 10:40:03 UTC
It's not hardmasked, it's been removed. And the --newuse behaviour is by design, not a bug. Read the reply Flameeyes posted on gentoo-dev ML please... (In reply to comment #1) > It's not hardmasked, it's been removed. And the --newuse behaviour is by > design, not a bug. Read the reply Flameeyes posted on gentoo-dev ML please... > did. posted this just before that. mr. warner's suggestion. see prior post ;) So, to re-state it here in case anyone else reads this bug in future: There's no way for portage to know whether a removed use flag has been removed because the feature is now hard-enabled or hard-disabled, so it just does the proper thing and forces re-emerge. Closing this. :) *** Bug 177080 has been marked as a duplicate of this bug. *** |