Summary: | EAPI 0 ebuilds won't pass QA because ${ED} variable is empty and read only | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Tomas Latal <gentoo> |
Component: | Core - External Interaction | Assignee: | Portage team <dev-portage> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | gentoo, mgorny, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tomas Latal
2022-10-05 08:31:00 UTC
Yes, indeed a real issue, although I think it's somewhat brave to continue using EAPI 0 given clearly nobody is testing these codepaths anymore. Is there a reason you are? Perhaps we should simply start removing support for old EAPIs from Portage. There's very little value in keeping them, and even less in putting an effort to fix them. (In reply to Sam James from comment #1) > Yes, indeed a real issue, although I think it's somewhat brave to continue > using EAPI 0 given clearly nobody is testing these codepaths anymore. Is > there a reason you are? Actually, this ebuild is pretty old, but is still doing its job satisfactory and there were no need to do a new ebuild just to bump EAPI... At least not for now. We have around 100 of those old packages in our overlay. But given that there were another EAPI 0 issue not long ago (Gentoo bug #869182), those codepaths are beginning to break down. (In reply to Michał Górny from comment #2) > Perhaps we should simply start removing support for old EAPIs from Portage. > There's very little value in keeping them, and even less in putting an > effort to fix them. I agree that removing old EAPIs can improve this situation in the long run (given the fact that those codepaths are not that well tested and it just complicates the code for Portage scripts such as QA). It will be easier to debug/prevent these kind of issues if the Portage just reports unsupported EAPI instead of just crashing the merge somewhere deep in QA scripts. And it would also be good when old EAPIs are removed if Portage could then report packages that have no ebuild with satisfactory EAPI (similar to "all suitable packages satisfying XY are masked"). |