| Summary: | Portage supports "myuse? foo/bar" syntax, PMS seems to not specify it | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Santiago M. Mola (RETIRED) <coldwind> |
| Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | pms |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 563798, 335925 | ||
As far as I know, it's deprecated along with ?:. I don't think it is at all illegal to support a superset of a given specification. repoman ought to catch that one (same for ?: iirc)... (In reply to comment #2) > I don't think it is at all illegal to support a superset of a given > specification. PMS includes wording about rejecting or warning for invalid inputs in various places. Ideally it'd take the Stroustrup approach and say that for everything... This is fixed in 2.1.9. |
Looking at Portage source code, it seems that it supports the following syntax for dependencies: "myuse? foo/bar" PMS secion 9.2 specifies use condition groups ("myuse? ( foo/bar )") but not the former syntax. Either portage should deprecate the old syntax, or PMS should be clarified.