| Summary: | check-reqs.eclass should not check requirements for binpkg installation | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | August Hörandl <hoea> |
| Component: | Current packages | Assignee: | Gentoo Quality Assurance Team <qa> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | jlec, marienz, nirbheek, python |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
August Hörandl
2012-06-10 20:36:40 UTC
The pypy ebuild uses the check-reqs eclass to check for enough ram, and the check-reqs eclass calls "die" for us if it's used from pkg_pretend. I think check-reqs_pkg_pretend should be a noop if MERGE_TYPE is "binary". QA team, as you're the maintainer of this eclass: could you make this change, or let me make it? The alternative would be for pypy to conditionally call check-reqs_pkg_pretend, but as this eclass is meant to be used for "ebuilds which have very high *build* requirements" it probably makes more sense for the eclass to do it, or many check-reqs users will accidentally incorrectly fail with binpkgs the way pypy does. (In reply to comment #1) Reminder: MERGE_TYPE was introduced in EAPI 4; its value is undefined in previous EAPI versions. So worst case, the improved logic works only in EAPI 4 or greater. That's why I mentioned checking for this in pkg_pretend, although I did not realize when I said that that the eclass uses *both* pkg_pretend and pkg_setup in EAPI 4. But yeah, I think this can only sensibly be fixed in EAPI 4. Meanwhile this bug was fixed by checking for MERGE_TYPE in pretend and setup |