Summary: | sys-apps/portage-2.2.0_alpha90 --newuse does not detect REQUIRED_USE conflict for built packages | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Paweł Rumian <gorkypl> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | gorkypl |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Paweł Rumian
2012-03-06 13:50:30 UTC
REQUIRED_USE is a build-time dependency, so apparently the REQUIRED_USE conflicts that you see were added only after you built the packages. So, it's not a problem until you try to rebuild the packages. Note that -u and -N imply --selective, so the commands with those options don't force a bunch of rebuilds like the other ones do. (In reply to comment #1) > Note that -u and -N imply --selective, so the commands with those options don't > force a bunch of rebuilds like the other ones do. Ah, now I understand. Thank you for explaining. I guess I can close the bug now? Yeah, I guess we could add another option like --newuse for this, but it's probably not worth the trouble. |