From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [RFC] What features should be included in EAPI 2?
Date: Wed, 13 Aug 2008 01:18:33 -0700 [thread overview]
Message-ID: <48A298D9.3030402@gentoo.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello again,
I'd like to get some feedback about what people would like to have
in the final EAPI 2. 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 in a short period of time. It
doesn't really makes sense to delay the EAPI bump too much for
implementation of new features, since those features can simply be
reserved for a future EAPI bump.
The latest experiment EAPI is 2_pre2, supported by
>=sys-apps/portage-2.2_rc7. Please refer to the html documentation
[1] for addition information about the experimental EAPI 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.
* Dependency atoms can be constrained to match specific USE flag
states, including USE conditional expressions embedded within
the atoms themselves.
* 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'.
In addition to the above extensions, I've received a patch for
SRC_URI arrows [2] that I plan to review but haven't had time yet.
Please file bugs for any additional features that you'd like to add
and mark them as blockers of bug 174380 [3].
Thanks,
Zac
[1]
http://dev.gentoo.org/~zmedico/portage/doc/portage.html#package-ebuild-eapi
[2] http://bugs.gentoo.org/show_bug.cgi?id=177863
[3] http://bugs.gentoo.org/show_bug.cgi?id=174380
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkiimNgACgkQ/ejvha5XGaOsCwCfYBAJNwTcl7USG/OF4lxI5iND
nD8An1lfyS6f5lvqXgeA1bXB3JHstyIi
=NGBs
-----END PGP SIGNATURE-----
next reply other threads:[~2008-08-13 8:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 8:18 Zac Medico [this message]
2008-08-13 12:03 ` [gentoo-dev] [RFC] What features should be included in EAPI 2? Ciaran McCreesh
2008-08-13 21:02 ` Zac Medico
2008-08-19 11:12 ` [gentoo-dev] " Steve Long
2008-08-19 12:45 ` Ciaran McCreesh
2008-08-19 18:01 ` Arun Raghavan
2008-08-19 18:18 ` Ciaran McCreesh
2008-08-19 20:27 ` [gentoo-dev] " Steve Long
2008-08-19 20:43 ` Ciaran McCreesh
2008-08-21 15:35 ` [gentoo-dev] " Steve Long
2008-08-21 15:58 ` Ciaran McCreesh
2008-08-22 2:26 ` Alec Warner
2008-08-23 14:15 ` [gentoo-dev] " Steve Long
2008-09-01 14:31 ` [gentoo-dev] " Peter Volkov
2008-08-27 3:15 ` [gentoo-dev] " Ryan Hill
2008-08-21 17:37 ` Thomas Anderson
2008-08-13 20:28 ` [gentoo-dev] " Petteri Räty
2008-08-13 21:07 ` Zac Medico
2008-08-13 22:55 ` Petteri Räty
2008-08-25 20:03 ` Jorge Manuel B. S. Vicetto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48A298D9.3030402@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox