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 1RFBe5-0007iu-9p for garchives@archives.gentoo.org; Sat, 15 Oct 2011 21:19:53 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9471C21C27E; Sat, 15 Oct 2011 21:19:44 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 16A2621C250 for ; Sat, 15 Oct 2011 21:19:19 +0000 (UTC) Received: from [192.168.168.169] (dyn-199-173-dsl.vsp.fi [83.146.199.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ssuominen) by smtp.gentoo.org (Postfix) with ESMTPSA id 114BD1B400A for ; Sat, 15 Oct 2011 21:19:17 +0000 (UTC) Message-ID: <4E99F8C6.1060601@gentoo.org> Date: Sun, 16 Oct 2011 00:19:02 +0300 From: Samuli Suominen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20111014 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 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> <4E98B88F.3010206@gentoo.org> <4E98BCD9.5060204@gentoo.org> <4E98DDA4.60002@gentoo.org> <4E98E7B8.7000102@gentoo.org> <4E99F461.1050203@gentoo.org> In-Reply-To: <4E99F461.1050203@gentoo.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: X-Archives-Hash: eac99a151884b1e0ed3659b3d1a39057 On 10/16/2011 12:00 AM, "Pawe=C5=82 Hajdan, Jr." wrote: > On 10/15/11 2:42 AM, Dirkjan Ochtman wrote: >> On Sat, Oct 15, 2011 at 03:54, Mike Gilbert wrote= : >>> That would be an ok approach from my perspective: We could just chang= e >>> line 14 of python.eclass and let package maintainers report breakage = as >>> they increment EAPI. I am confident that nothing EAPI <=3D 3 would br= eak. >>> >>> Is anyone (especially djc and the python herd members) opposed to thi= s? >> >> Seems fine to me; I can't really think of a practical better way. >=20 > Thank you, change committed to CVS then. Hopefully nobody will get upse= t > about this. >=20 > I'll wait a few days before I start using EAPI-4 in ebuilds using > python.eclass, but I've done local tests and everything works fine (for > the ebuild I (co-)maintain). >=20 Thanks, this is most appericiated. This allowed me to kill EAPI=3D3 support from xfconf.eclass.