-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Donnie Berkholz wrote: > Here's the agenda. I'm eagerly awaiting submission of EAPI 2, whenever > folks are ready.
I've updated the EAPI 2 draft to remove the eapi* functions and the gitweb unpack extension as mentioned earlier in Jorge's email [1]. The html version of the draft is posted in my dev space [2] and is also attached directly to this email. All of the extensions are summarized below: * The 'doman' helper function recognizes language codes in man page source files, and uses them to generate an appropriate installation path. * 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. * The default phase function implementation for the currently executing phase is accessible as a function named 'default'. [1] http://archives.gentoo.org/gentoo-dev/msg_2124e5ac0da4c1928d96a7186a81a0a3.xml [2] http://dev.gentoo.org/~zmedico/portage/eapi/eapi-2-draft.html - -- Thanks, Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjIvigACgkQ/ejvha5XGaM8VACgtdpQQaHg6M/ZVH6sYvrTdeEF PfwAoLJx1wn5le/0GZReFGaFQM7F5RND =SY0M -----END PGP SIGNATURE-----Title: EAPI 2 Draft
Blocker atoms which use the previously existing !atom syntax now have a slightly different meaning. These blocker atoms indicate that conflicting packages may be temporarily installed simultaneously. When temporary simultaneous installation of conflicting packages occurs, the installation of a newer package may overwrite any colliding files that belong to an older package which is explicitly blocked. When such file collisions occur, the colliding files cease to belong to the older package, and they remain installed after the older package is eventually uninstalled. The older package is uninstalled only after any newer blocking packages have been merged on top of it.
A new !!atom syntax is now supported, for use in special cases for which temporary simultaneous installation of conflicting packages should not be allowed. If a given package happens to be blocked my a mixture of atoms consisting of both the !atom and !!atom syntaxes, the !!atom syntax takes precedence over the !atom syntax.
A new syntax is supported which allows customization of the output file name for a given URI. In order to customize the output file name, a given URI should be followed by a "->" operator which, in turn, should be followed by the desired output file name. As usual, all tokens, including the operator and output file name, should be separated by whitespace.
A new src_prepare function is called after the src_unpack function, with cwd initially set to $S.
The configure portion of the src_compile function has been split into a separate function which is named src_configure. The src_configure function is called in-between the src_prepare and src_compile functions.
src_configure() {
if [[ -x ${ECONF_SOURCE:-.}/configure ]] ; then
econf
fi
}
src_compile() {
if [ -f Makefile ] || [ -f GNUmakefile ] || [ -f makefile ] ; then
emake || die "emake failed"
fi
}
Table 6.11. Execution Order of Phase Functions
| Phase Function Name |
|---|
| pkg_setup |
| src_unpack |
| src_prepare |
| src_configure |
| src_compile |
| src_test |
| src_install |
| pkg_preinst |
| pkg_postinst |
| pkg_prerm |
| pkg_postrm |
The default pkg_nofetch and src_* phase functions are now accessible via a function having a name that begins with default_ and ends with the respective phase function name. For example, a call to a function with the name default_src_compile is equivalent to a call to the default src_compile implementation.
Table 6.12. Default Phase Functions
| Function Name |
|---|
| default_pkg_nofetch |
| default_src_unpack |
| default_src_prepare |
| default_src_configure |
| default_src_compile |
| default_src_test |
A function named "default" is redefined for each phase so that it will call the default_* function corresponding to the current phase. For example, a call to the function named "default" during the src_compile phase is equivalent to a call to the function named default_src_compile.
eapi-2-draft.html.sig
Description: Binary data
