Gentoo Archives: gentoo-dev

From: Doug Goldstein <cardoe@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] EAPI-2
Date: Tue, 09 Sep 2008 04:36:53
Message-Id: 48C5FD58.7060300@gentoo.org
In Reply to: [gentoo-dev] EAPI-2 by "Jorge Manuel B. S. Vicetto"
1 Jorge Manuel B. S. Vicetto wrote:
2 > -----BEGIN PGP SIGNED MESSAGE-----
3 > Hash: SHA1
4 >
5 > Hi again.
6 >
7 > Quoting Zac earlier in #gentoo-portage:
8 >
9 > 21:46 < zmedico> jmbsvicetto: I think we essentially have a spec already
10 > that people can agree on. just take my draft and subtract the eapi*
11 > functions and the gitweb unpack extension.
12 >
13 > So we're talking about adding the following to EAPI-2:
14 >
15 > ~ * The 'doman' helper function recognizes language codes in man page
16 > ~ source files, and uses them to generate an appropriate
17 > ~ installation path.
18 >
19 > ~ * The meaning of the !atom blocker syntax now implies that
20 > ~ temporary simultaneous installation of conflicting packages is
21 > ~ allowed [3].
22 >
23 > ~ * A new !!atom blocker syntax is now supported, for use in special
24 > ~ cases in which temporary simultaneous installation of conflicting
25 > ~ packages should not be allowed.
26 >
27 > ~ * Dependency atoms can be constrained to match specific USE flag
28 > ~ states, including USE conditional expressions embedded within
29 > ~ the atoms themselves.
30 >
31 > ~ * SRC_URI supports a syntax extension which allows customization
32 > ~ of output file names by using a "->" operator.
33 >
34 > ~ * A new src_prepare phase function is called after src_unpack.
35 >
36 > ~ * The old src_compile phase function is split into separate
37 > ~ src_configure and src_compile fuctions.
38 >
39 > ~ * Default phase function implementations for the current EAPI are
40 > ~ accessible via a function having a name that begins with default_
41 > ~ and ends with the respective phase function name.
42 >
43 > ~ * The default phase function implementation for the currently
44 > ~ executing phase is accessible as a function named 'default'.
45 >
46 > Given the earlier discussion about EAPI-2 in
47 > http://archives.gentoo.org/gentoo-dev/msg_3e9d42191c3537c4f699c12cadd0ad99.xml
48 >
49 > and cardoe's earlier request to the council ml, can the council members
50 > discuss this proposal and consider voting it?
51 > Does anyone have any objections to this proposal?
52 >
53 > - --
54 > Regards,
55 >
56 > Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
57 > Gentoo- forums / Userrel / Devrel / SPARC / KDE
58 > -----BEGIN PGP SIGNATURE-----
59 > Version: GnuPG v2.0.9 (GNU/Linux)
60 > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
61 >
62 > iEYEARECAAYFAkjFtoQACgkQcAWygvVEyALQigCePXcGlT5m6JGB2OlB5swY6f4F
63 > /yIAnRte3mm5PULg73j5KDrnKHSFB5h6
64 > =lW1u
65 > -----END PGP SIGNATURE-----
66 >
67 That removes the only two sections that appeared to have any chatter on
68 them. Anyone involved in PMS or other package managers have any input on
69 this?