| Summary: | sys-apps/portage-2.3.6: -* in profile package.use is reported as "Invalid USE flag" | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Zac Medico <zmedico> |
| Component: | Core - Configuration | Assignee: | Portage team <dev-portage> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | mgorny, pms |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=623984 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Zac Medico
2017-07-04 22:44:44 UTC
That's probably correct. The PMS doesn't really cover wildcards there, I think. Currently, PMS specifies -* only for KEYWORDS and for incremental variables in make.defaults: https://projects.gentoo.org/pms/6/pms.html#x1-620005.3.1 Given that package.use represents per-package USE, doesn't it follow that it should support -* like USE does? Portage already allows this in user configuration. It just doesn't work in profiles. Maybe that would be more consistent, but the spec simply doesn't say so. We can make it a feature in EAPI 7. OTOH, it seems that there was little need for it, or the issue would have been raised earlier. (In reply to Ulrich Müller from comment #4) > Maybe that would be more consistent, but the spec simply doesn't say so. In the case of Portage, it seems like -* support was accidentally disabled in this commit: https://github.com/gentoo/portage/commit/9e9c822aae0c3daab208175025b161d6d34877fe > We can make it a feature in EAPI 7. OTOH, it seems that there was little > need for it, or the issue would have been raised earlier. I would prefer to change the behavior, in order to make it more consistent. |
