Summary: | portage rebuilds kde-base/kate-4.10.3:4 just because additional python-3.3 target | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Ulenrich <ulenrich> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | bkohler |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ulenrich
2013-05-31 00:26:17 UTC
If you want to ignore these kinds of USE changes were a disabled flag was added or removed, try --changed-use in place of --newuse. Portage doesn't know if the new-but-disabled USE flag is adding a new feature that you still have disabled, or if an existing feature has just been made optional and you are NOW disabling it. But you can make it go one way or the other with --changed-use or --newuse. Uups, thank you Ben Kohler for explanation and hint. Just my incompetence ... |