"Wulf C. Krueger" <[EMAIL PROTECTED]> said: > "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."
Okay, so I stand corrected about them approving it. Where is the approved specification though? PMS is still a draft the last time I heard, and if it isn't, we should have a non-moving version that is authoritive about EAPI=1. (And no, the man pages are not a specification, nor is a list of bugs...give us one document that we can point to) I can get it put into devmanual as soon as I can find the approved authoritative source to base information off of. -- Mark Loeser email - halcy0n AT gentoo DOT org email - mark AT halcy0n DOT com web - http://www.halcy0n.com
pgpsrvHQTUf4T.pgp
Description: PGP signature
