| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hi everyone, |
| 5 |
|
| 6 |
Please review and discuss the following features which are proposed |
| 7 |
for inclusion EAPI 2. As mentioned in my previous email [1], in |
| 8 |
planning for this EAPI bump, we should strike a balance somewhere |
| 9 |
in-between everything that we'd like to have and whatever we can |
| 10 |
implement and agree on in a short period of time. It doesn't make a |
| 11 |
lot of sense to delay the EAPI bump too much for implementation or |
| 12 |
debate of new features, since those features can simply be reserved |
| 13 |
for EAPI 3. |
| 14 |
|
| 15 |
Refer to the html documentation [2] for addition information about |
| 16 |
the proposed EAPI 2 extensions which are summarized here: |
| 17 |
|
| 18 |
* The 'doman' helper function recognizes language codes in man page |
| 19 |
source files, and uses them to generate an appropriate |
| 20 |
installation path. |
| 21 |
|
| 22 |
* The 'unpack' helper function recognizes ;sf=tbz2 and ;sf=tgz |
| 23 |
extensions, for interoperability with gitweb. |
| 24 |
|
| 25 |
* The meaning of the !atom blocker syntax now implies that |
| 26 |
temporary simultaneous installation of conflicting packages is |
| 27 |
allowed [3]. |
| 28 |
|
| 29 |
* A new !!atom blocker syntax is now supported, for use in special |
| 30 |
cases in which temporary simultaneous installation of conflicting |
| 31 |
packages should not be allowed. |
| 32 |
|
| 33 |
* Dependency atoms can be constrained to match specific USE flag |
| 34 |
states, including USE conditional expressions embedded within |
| 35 |
the atoms themselves. |
| 36 |
|
| 37 |
* SRC_URI supports a syntax extension which allows customization |
| 38 |
of output file names by using a "->" operator. |
| 39 |
|
| 40 |
* A new src_prepare phase function is called after src_unpack. |
| 41 |
|
| 42 |
* The old src_compile phase function is split into separate |
| 43 |
src_configure and src_compile fuctions. |
| 44 |
|
| 45 |
* Default phase function implementations for the current EAPI are |
| 46 |
accessible via a function having a name that begins with default_ |
| 47 |
and ends with the respective phase function name. |
| 48 |
|
| 49 |
* Default phase function implementations for older EAPIs are |
| 50 |
accessible via functions having names that start with 'eapi', |
| 51 |
followed by the EAPI value. |
| 52 |
|
| 53 |
* The default phase function implementation for the currently |
| 54 |
executing phase is accessible as a function named 'default'. |
| 55 |
|
| 56 |
Many of the above extensions have already been discussed in the |
| 57 |
previous thread [1], so please continue discussion there if |
| 58 |
necessary. You can file bugs for any additional features that you'd |
| 59 |
like to add and mark them as blockers of bug 174380 [4]. |
| 60 |
|
| 61 |
[1] |
| 62 |
http://archives.gentoo.org/gentoo-dev/msg_2ed72695ac75d0f80ddd579ef55c320a.xml |
| 63 |
[2] |
| 64 |
http://dev.gentoo.org/~zmedico/portage/doc/portage.html#package-ebuild-eapi-2-draft |
| 65 |
[3] |
| 66 |
http://archives.gentoo.org/gentoo-dev/msg_2551bea5c002093d5bacc26723208d93.xml |
| 67 |
[4] http://bugs.gentoo.org/show_bug.cgi?id=174380 |
| 68 |
- -- |
| 69 |
Thanks, |
| 70 |
Zac |
| 71 |
-----BEGIN PGP SIGNATURE----- |
| 72 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 73 |
|
| 74 |
iEYEARECAAYFAkjAZ/sACgkQ/ejvha5XGaO3FACfVDzAByYYfU9buY7oJo2ytc/K |
| 75 |
lJQAn1oLi0uknAdPhVW7hELDT1FXvXX5 |
| 76 |
=K/em |
| 77 |
-----END PGP SIGNATURE----- |
Archives