Summary: | sys-apps/portage: conflicting use flags should be sanity checked | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Raymond Jennings <shentino> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | enhancement | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Raymond Jennings
2017-03-01 04:50:44 UTC
A similiar check on the portage tree's profiles may also prove useful as a QA test. Different levels can override each other, but there's provable ambiguity if it's in the same layer. IMHO, detection of such a blatant contradiction should be an error. It would be valid to do something like this for quick local overrides though. I'm not sure we're that bothered about this. I feel like it'd be a lot of effort to implement with very little gain, but I suppose the confusion isn't great when hitting this problem? |