From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1REphG-0000sc-B1 for garchives@archives.gentoo.org; Fri, 14 Oct 2011 21:53:42 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EEC6521C0ED; Fri, 14 Oct 2011 21:53:33 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id E6C2A21C0BD for ; Fri, 14 Oct 2011 21:53:07 +0000 (UTC) Received: from [172.2.88.37] (unknown [216.91.134.253]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id 02C3D1B4022; Fri, 14 Oct 2011 21:53:06 +0000 (UTC) Message-ID: <4E98AF3B.40405@gentoo.org> Date: Fri, 14 Oct 2011 17:52:59 -0400 From: Mike Gilbert User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 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 CC: python@gentoo.org Subject: Re: [gentoo-dev] python.eclass EAPI 4 support, this gets really annoying References: <4E8766F1.2020609@gentoo.org> <20111014193958.GA3465@localhost> <4E98A793.8050806@gentoo.org> In-Reply-To: X-Enigmail-Version: 1.3.2 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enig5431BDA480A5B7F02B3690FF" X-Archives-Salt: X-Archives-Hash: 89ca7c56c6ddf709151622215f5c5eb2 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5431BDA480A5B7F02B3690FF Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 10/14/2011 5:28 PM, Matt Turner wrote: > On Fri, Oct 14, 2011 at 5:25 PM, Matthew Summers > wrote: >> Its being worked on currently. There are many fairly difficult issues >> to be worked through here. >=20 > That's kind of the question though. What's are the issues? The only issue that has been raised is that the eclass will die if python_pkg_setup is not called from the ebuild. This can happen either implicitly (the function is exported) or explicitly (by calling it from pkg_setup). I haven't gotten a very good explanation as to why this is necessary from Arfrever. He has given some very short, non-informative explanations like "Jython requires it". Puzzling it out myself takes quite a bit of brain power, given the complexity of the eclass. There may in fact be no reason for it at all. Either way, somebody needs to actually understand it. Other than that issue, I think we really just need to do some testing. Despite there being a large number of people in the python herd, there aren't many who actually have the time to do this. It would be helpful if folks could brain storm a list of python related packages to test under EAPI 4. I may have some time over the next few weekends to work on this. --------------enig5431BDA480A5B7F02B3690FF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) iF4EAREIAAYFAk6Yr0AACgkQC77qH+pIQ6Rp0gD/XLLrKSSvMMD5GxMIV2ApxrCA RCcVpnYZbdbpeLz/PJsA/jcER2jGAe4BXEkeT45L4WuBSNm0+GOeMGsvFcYQnXco =dDjv -----END PGP SIGNATURE----- --------------enig5431BDA480A5B7F02B3690FF--