-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone,
Please review and discuss the following features which are proposed for inclusion EAPI 2. As mentioned in my previous email [1], in planning for this EAPI bump, we should strike a balance somewhere in-between everything that we'd like to have and whatever we can implement and agree on in a short period of time. It doesn't make a lot of sense to delay the EAPI bump too much for implementation or debate of new features, since those features can simply be reserved for EAPI 3. Refer to the html documentation [2] for addition information about the proposed EAPI 2 extensions which are summarized here: * The 'doman' helper function recognizes language codes in man page source files, and uses them to generate an appropriate installation path. * The 'unpack' helper function recognizes ;sf=tbz2 and ;sf=tgz extensions, for interoperability with gitweb. * The meaning of the !atom blocker syntax now implies that temporary simultaneous installation of conflicting packages is allowed [3]. * A new !!atom blocker syntax is now supported, for use in special cases in which temporary simultaneous installation of conflicting packages should not be allowed. * Dependency atoms can be constrained to match specific USE flag states, including USE conditional expressions embedded within the atoms themselves. * SRC_URI supports a syntax extension which allows customization of output file names by using a "->" operator. * A new src_prepare phase function is called after src_unpack. * The old src_compile phase function is split into separate src_configure and src_compile fuctions. * Default phase function implementations for the current EAPI are accessible via a function having a name that begins with default_ and ends with the respective phase function name. * Default phase function implementations for older EAPIs are accessible via functions having names that start with 'eapi', followed by the EAPI value. * The default phase function implementation for the currently executing phase is accessible as a function named 'default'. Many of the above extensions have already been discussed in the previous thread [1], so please continue discussion there if necessary. You can file bugs for any additional features that you'd like to add and mark them as blockers of bug 174380 [4]. [1] http://archives.gentoo.org/gentoo-dev/msg_2ed72695ac75d0f80ddd579ef55c320a.xml [2] http://dev.gentoo.org/~zmedico/portage/doc/portage.html#package-ebuild-eapi-2-draft [3] http://archives.gentoo.org/gentoo-dev/msg_2551bea5c002093d5bacc26723208d93.xml [4] http://bugs.gentoo.org/show_bug.cgi?id=174380 - -- Thanks, Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjAZ/sACgkQ/ejvha5XGaO3FACfVDzAByYYfU9buY7oJo2ytc/K lJQAn1oLi0uknAdPhVW7hELDT1FXvXX5 =K/em -----END PGP SIGNATURE-----
