From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1KXiHV-00044N-Q2 for garchives@archives.gentoo.org; Mon, 25 Aug 2008 20:03:18 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C56BDE0423; Mon, 25 Aug 2008 20:03:16 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 9DBB0E0423 for ; Mon, 25 Aug 2008 20:03:16 +0000 (UTC) Received: from [192.168.1.64] (bl4-221-87.dsl.telepac.pt [81.193.221.87]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 21AA565F05 for ; Mon, 25 Aug 2008 20:03:14 +0000 (UTC) Message-ID: <48B30FFB.8020009@gentoo.org> Date: Mon, 25 Aug 2008 20:03:07 +0000 From: "Jorge Manuel B. S. Vicetto" User-Agent: Thunderbird 2.0.0.16 (X11/20080727) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] What features should be included in EAPI 2? References: <48A298D9.3030402@gentoo.org> In-Reply-To: <48A298D9.3030402@gentoo.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: d233dfa7-0acc-4649-a582-9d7ea54380cc X-Archives-Hash: cf016d9193892161dea8681c31251785 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi. Zac Medico wrote: | 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. Are there any other features that should be included in EAPI-2? Does anyone have any objections to the features Zac listed? | 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 - -- Regards, Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org Gentoo- forums / Userrel / SPARC / KDE -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkizD/sACgkQcAWygvVEyAKb6ACfd3ODwtS0LzGyblGdvsfnXCkn xuMAn0FwJV6C0sTY5uFYp/OmSLmbrihb =kWTD -----END PGP SIGNATURE-----