Summary: | Portage shouldn't check $EAPI to get the EAPI | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Ciaran McCreesh <ciaran.mccreesh> |
Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | betelgeuse, sera, ulm |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 410999 | ||
Bug Blocks: |
Description
Ciaran McCreesh
2012-04-06 18:02:03 UTC
(In reply to comment #0) > The easiest fix is probably to set an "unlikely to need to be tampered with" > variable like PORTAGE_ACTUAL_EAPI and to use that. And keep the council apprised of the actual realities (ebuild flow, gotchas, take your pick) of this decision. Council removed from CC as discussed in today's meeting. |