Gentoo Logo
Gentoo Spaceship

Installation:
Gentoo Handbook
Installation Docs

Documentation:
Home
Listing
About Gentoo
Philosophy
Social Contract

Resources:
Bug Tracker
Developer List
Discussion Forums
Gentoo BitTorrents
Gentoo Linux Enhancement Proposals
IRC Channels
Mailing Lists
Mirrors
Name and Logo Guidelines
Online Package Database
Security Announcements
Staffing Needs
Supporting Vendors
View our CVS

Graphics:
Logos and themes
Icons
ScreenShots

Miscellaneous Resources:
Gentoo Linux Store
Gentoo-hosted projects
IBM dW/Intel article archive




List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Zac Medico <zmedico@g.o>
Subject: Re: One-Day Gentoo Council Reminder for September
Date: Wed, 10 Sep 2008 23:43:54 -0700
-----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-----
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>EAPI 2 Draft</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="Portage Documentation" /><link rel="up" href="ch06s03.html" title="EAPI" /><link rel="prev" href="ch06s03s04.html" title="EAPI 2_pre2" /><link rel="next" href="pt04.html" title="Part IV. Quality Assurance" /></head><body><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="package-ebuild-eapi-2-draft"></a>EAPI 2 Draft</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-helpers">Helpers</a></span></dt><dd><dl><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-helpers-doman">doman</a></span></dt><dd><dl><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-helpers-doman-language-codes">Recognition of Language Codes in File Names</a></span></dt></dl></dd></dl></dd><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-metadata">Metadata</a></span></dt><dd><dl><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-metadata-dependencies">Dependencies</a></span></dt><dd><dl><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-metadata-dependencies-blocker-atoms">Blocker Atoms</a></span></dt><dd><dl><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-metadata-dependencies-blocker-atoms-new-meaning">New Meaning for Old Syntax</a></span></dt><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-metadata-dependencies-blocker-atoms-new-syntax">New !!atom Syntax</a></span></dt></dl></dd><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-metadata-dependencies-use">USE Dependencies</a></span></dt><dd><dl><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-metadata-dependencies-use-unconditional">Unconditional USE Dependencies</a></span></dt><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-metadata-dependencies-use-conditional">Conditional USE Dependencies</a></span></dt></dl></dd></dl></dd><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-metadata-src-uri">SRC_URI</a></span></dt><dd><dl><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-metadata-src-uri-output-file-name-customization">Customization of Output File Names</a></span></dt></dl></dd></dl></dd><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-phases">Phases</a></span></dt><dd><dl><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-phases-src-prepare">New src_prepare Phase Function</a></span></dt><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-phases-src-configure">New src_configure Phase Function</a></span></dt><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-phases-order">Execution Order of Phase Functions</a></span></dt><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-phases-default-functions">Default Phase Functions</a></span></dt><dt><span class="section"><a href="#package-ebuild-eapi-2-draft-phases-default-function-alias">Default Phase Function Alias</a></span></dt></dl></dd></dl></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="package-ebuild-eapi-2-draft-helpers"></a>Helpers</h4></div></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h5 class="title"><a id="package-ebuild-eapi-2-draft-helpers-doman"></a>doman</h5></div></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h6 class="title"><a id="package-ebuild-eapi-2-draft-helpers-doman-language-codes"></a>Recognition of Language Codes in File Names</h6></div></div></div><p>
	Language codes in file names are now used for path translation.
	</p><div class="table"><a id="id2565871"></a><p class="title"><b>Table 6.8. Man Page Path Translation</b></p><div class="table-contents"><table summary="Man Page Path Translation" border="1"><colgroup><col align="left" /><col align="left" /></colgroup><thead><tr><th align="left">Source</th><th align="left">Destination</th></tr></thead><tbody><tr><td align="left">foo.1</td><td align="left">/usr/share/man/man1/foo.1</td></tr><tr><td align="left">foo.lang.1</td><td align="left">/usr/share/man/lang/man1/foo.1</td></tr></tbody></table></div></div><br class="table-break" /></div></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="package-ebuild-eapi-2-draft-metadata"></a>Metadata</h4></div></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h5 class="title"><a id="package-ebuild-eapi-2-draft-metadata-dependencies"></a>Dependencies</h5></div></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h6 class="title"><a id="package-ebuild-eapi-2-draft-metadata-dependencies-blocker-atoms"></a>Blocker Atoms</h6></div></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h6 class="title"><a id="package-ebuild-eapi-2-draft-metadata-dependencies-blocker-atoms-new-meaning"></a>New Meaning for Old Syntax</h6></div></div></div><p>
	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.
	</p></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h6 class="title"><a id="package-ebuild-eapi-2-draft-metadata-dependencies-blocker-atoms-new-syntax"></a>New !!atom Syntax</h6></div></div></div><p>
	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.
	</p></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h6 class="title"><a id="package-ebuild-eapi-2-draft-metadata-dependencies-use"></a>USE Dependencies</h6></div></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h6 class="title"><a id="package-ebuild-eapi-2-draft-metadata-dependencies-use-unconditional"></a>Unconditional USE Dependencies</h6></div></div></div><div class="table"><a id="id2566027"></a><p class="title"><b>Table 6.9. Syntax Examples</b></p><div class="table-contents"><table summary="Syntax Examples" border="1"><colgroup><col align="left" /><col align="left" /></colgroup><thead><tr><th align="left">Example</th><th align="left">Meaning</th></tr></thead><tbody><tr><td align="left">foo[bar]</td><td align="left">foo must have bar enabled</td></tr><tr><td align="left">foo[bar,baz]</td><td align="left">foo must have both bar and baz enabled</td></tr><tr><td align="left">foo[-bar,baz]</td><td align="left">foo must have bar disabled and baz enabled</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h6 class="title"><a id="package-ebuild-eapi-2-draft-metadata-dependencies-use-conditional"></a>Conditional USE Dependencies</h6></div></div></div><div class="table"><a id="id2566107"></a><p class="title"><b>Table 6.10. Syntax Examples</b></p><div class="table-contents"><table summary="Syntax Examples" border="1"><colgroup><col align="left" /><col align="left" /></colgroup><thead><tr><th align="left">Compact Form</th><th align="left">Equivalent Expanded Form</th></tr></thead><tbody><tr><td align="left">foo[bar?]</td><td align="left">bar? ( foo[bar]  ) !bar? ( foo       )</td></tr><tr><td align="left">foo[!bar?]</td><td align="left">bar? ( foo       ) !bar? ( foo[-bar] )</td></tr><tr><td align="left">foo[bar=]</td><td align="left">bar? ( foo[bar]  ) !bar? ( foo[-bar] )</td></tr><tr><td align="left">foo[!bar=]</td><td align="left">bar? ( foo[-bar] ) !bar? ( foo[bar]  )</td></tr></tbody></table></div></div><br class="table-break" /></div></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h5 class="title"><a id="package-ebuild-eapi-2-draft-metadata-src-uri"></a>SRC_URI</h5></div></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h6 class="title"><a id="package-ebuild-eapi-2-draft-metadata-src-uri-output-file-name-customization"></a>Customization of Output File Names</h6></div></div></div><p>
			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 "-&gt;" 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.
			</p></div></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="package-ebuild-eapi-2-draft-phases"></a>Phases</h4></div></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h5 class="title"><a id="package-ebuild-eapi-2-draft-phases-src-prepare"></a>New src_prepare Phase Function</h5></div></div></div><p>
			A new src_prepare function is called after the src_unpack
			function, with cwd initially set to $S.
			</p></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h5 class="title"><a id="package-ebuild-eapi-2-draft-phases-src-configure"></a>New src_configure Phase Function</h5></div></div></div><p>
			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.
			</p><pre class="programlisting">
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
}
			</pre></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h5 class="title"><a id="package-ebuild-eapi-2-draft-phases-order"></a>Execution Order of Phase Functions</h5></div></div></div><div class="table"><a id="id2566284"></a><p class="title"><b>Table 6.11. Execution Order of Phase Functions</b></p><div class="table-contents"><table summary="Execution Order of Phase Functions" border="1"><colgroup><col align="left" /></colgroup><thead><tr><th align="left">Phase Function Name</th></tr></thead><tbody><tr><td align="left">pkg_setup</td></tr><tr><td align="left">src_unpack</td></tr><tr><td align="left">src_prepare</td></tr><tr><td align="left">src_configure</td></tr><tr><td align="left">src_compile</td></tr><tr><td align="left">src_test</td></tr><tr><td align="left">src_install</td></tr><tr><td align="left">pkg_preinst</td></tr><tr><td align="left">pkg_postinst</td></tr><tr><td align="left">pkg_prerm</td></tr><tr><td align="left">pkg_postrm</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h5 class="title"><a id="package-ebuild-eapi-2-draft-phases-default-functions"></a>Default Phase Functions</h5></div></div></div><p>
			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.
			</p><div class="table"><a id="id2566404"></a><p class="title"><b>Table 6.12. Default Phase Functions</b></p><div class="table-contents"><table summary="Default Phase Functions" border="1"><colgroup><col align="left" /></colgroup><thead><tr><th align="left">Function Name</th></tr></thead><tbody><tr><td align="left">default_pkg_nofetch</td></tr><tr><td align="left">default_src_unpack</td></tr><tr><td align="left">default_src_prepare</td></tr><tr><td align="left">default_src_configure</td></tr><tr><td align="left">default_src_compile</td></tr><tr><td align="left">default_src_test</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h5 class="title"><a id="package-ebuild-eapi-2-draft-phases-default-function-alias"></a>Default Phase Function Alias</h5></div></div></div><p>
			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.
			</p></div></div></div></body></html>
Attachment:
eapi-2-draft.html.sig (Binary data)
Replies:
Re: One-Day Gentoo Council Reminder for September
-- Ciaran McCreesh
References:
One-Day Gentoo Council Reminder for September
-- Mike Frysinger
Re: One-Day Gentoo Council Reminder for September
-- Donnie Berkholz
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: One-Day Gentoo Council Reminder for September
Next by thread:
Re: One-Day Gentoo Council Reminder for September
Previous by date:
Re: Hi
Next by date:
Re: One-Day Gentoo Council Reminder for September


Updated Jun 17, 2009

Donate to support our development efforts.

Gentoo Centric Hosting: vr.org

VR Hosted

Tek Alchemy

Tek Alchemy

SevenL.net

SevenL.net

php|architect

php|architect

Copyright 2001-2007 Gentoo Foundation, Inc. Questions, Comments? Email www@gentoo.org.