On Wednesday, 13. February 2008 18:57:58 Mark Loeser wrote: > This is probably a bit late to be bringing up, but could the council > please discuss the state of PMS and EAPI? What we mean by that is that > it seems we are using EAPI=1 in the tree, and some of us are concerned > because we can't find any council approved proposal of what EAPI=1 > actually means.
"EAPI=1 approved for use in the main tree ---------------------------------------- Stable portage version 2.1.3.12 supports EAPI=1. It's now officially OK to start using it in the main tree. From the ebuild ChangeLog for portage: This release is the first to have support for EAPI-1 (#194876), which includes SLOT dependencies (#174405), IUSE defaults (#174410), and ECONF_SOURCE support for the default src_compile function (#179380). Package maintainers should carefully consider the backward compatibility consequences before defining EAPI="1" in any ebuilds, especially if other packages depend on those ebuilds. See the ebuild(5) and emerge(1) manual pages for EAPI related documentation. EAPI=1 features are documented in PMS as well as the man pages, but they are not yet documented in the devmanual or the dev handbook." (From http://www.gentoo.org/proj/en/council/meeting-logs/20071108-summary.txt) -- Best regards, Wulf
signature.asc
Description: This is a digitally signed message part.
