Summary: | package.mask should support repo constraints | ||
---|---|---|---|
Product: | Portage Development | Reporter: | SpanKY <vapier> |
Component: | Core - Configuration | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | enhancement | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
SpanKY
![]() Don't we have a layout.conf key for this? (In reply to Michał Górny from comment #1) > Don't we have a layout.conf key for this? No, but we can add one. You can use repo atoms now if you put "5-progress" in an eapi file in the same directory. (In reply to Zac Medico from comment #2) i had tried "5" before posting, but i guess the other part i was missing was that eapi is a contained value. when doing both those things, it does work. wrt layout.conf key, i think the existing profile_eapi_when_unspecified key (while a bit verbose) should be sufficient for our needs. |