Summary: | ebuild skips EAPI unsupported phases silently | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Richard <shiningarcanine> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | UNCONFIRMED --- | ||
Severity: | enhancement | CC: | jer |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://devmanual.gentoo.org/ebuild-writing/eapi/index.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Richard
2011-08-23 15:40:50 UTC
The ebuild has EAPI=1 so src_configure is not a valid build phase and is ignored, which is fine. The problem you are looking at is that ebuild(1) should probably fail when an invalid phase is called. ebuild does abort for generally invalid phases (try "ebuild ... foo"), but it silently skips invalid ones based on the active EAPI |