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 1Phj2a-00047b-QY for garchives@archives.gentoo.org; Tue, 25 Jan 2011 13:34:37 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 10433E0C2A; Tue, 25 Jan 2011 13:34:27 +0000 (UTC) Received: from tommyserver.de (tommyserver.de [85.14.198.51]) by pigeon.gentoo.org (Postfix) with ESMTP id 737E3E0BFC for ; Tue, 25 Jan 2011 13:33:53 +0000 (UTC) Received: from [192.168.178.22] (p57ADF020.dip.t-dialin.net [87.173.240.32]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tommyserver.de (Postfix) with ESMTPSA id 428FCED6C for ; Tue, 25 Jan 2011 14:33:51 +0100 (CET) Message-ID: <4D3ED13B.701@gentoo.org> Date: Tue, 25 Jan 2011 14:33:47 +0100 From: Thomas Sachau 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] EAPI usage in main tree References: <4D3EB1FE.1020805@gentoo.org> In-Reply-To: <4D3EB1FE.1020805@gentoo.org> X-Enigmail-Version: 1.1.2 OpenPGP: id=211CA2D4 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enigD1C2CB24E516ECCACA7E9B4B" X-Archives-Salt: X-Archives-Hash: b03a98dc7c7b43e9fa293c7aea33e4da This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD1C2CB24E516ECCACA7E9B4B Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am 25.01.2011 12:20, schrieb Tom=C3=A1=C5=A1 Chv=C3=A1tal: > Hi, > I would like to upgrade tree-wide policy for EAPI usage in main tree. > Currently we say that developers can use any named version they wish or= > find sufficient. > I would on other hand like to have all ebuilds to use Latest EAPI > version possible (given the eclasses support it [hint hint maintainers > of eclasses should always try to support latest :P]) with expection for= > base-system or more specialy depgraph for portage that needs to be > EAPI0. [[ And here we need to find out some upgrade proccess that would= > work for everyone so we could somehow migrate them too :)]] >=20 > With this usually new developers should be aware only of latest EAPI an= d > wont need to memorize what which EAPI support. Heck even I sometimes > forget what i can do with some version and whatnot. Do you have some more arguments for your request? Most new developers wil= l have to know about all EAPi versions anyway since they join an existing team with existing ebuil= ds, which will mostly not use the newest EAPI. As an argument againt this: Noone forces you to keep older EAPI versions = of the ebuilds you maintain, you can always bump them to the latest EAPI. But why do you wan= t to force this on all developers? If i have an EAPI-0 ebuild and am fine with it, why should i = convert it to the latest EAPI? >=20 > Winner for being PITA in this race is python.eclass that HAS completely= > different behavior based on EAPI version used... The python eclass issues are not just EAPI related, the complete eclass i= s very complex and hard to read/understand. And just because the eclass has additional EAPI-specific= behaviour, this is specific to this eclass and should not be an argument for the general EAP= I discussion. >=20 > Cheers >=20 > Tomas --=20 Thomas Sachau Gentoo Linux Developer --------------enigD1C2CB24E516ECCACA7E9B4B 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 (GNU/Linux) iJwEAQEKAAYFAk0+0UEACgkQG7kqcTWJkGcRVQQAuy7REC4xskA2Q14oLT0PwpG/ skrxZQqmD5nN1mvQcXIMj2FcsNd9GPioOURj0cX2ZEd+03eLZaeYfdifHbxSh4u/ oZj1Nr0iXh9OTZd8F28TD/3OYgJSAzSMz9B7KTsi4P6o678kZ5kro9XOB4fStRsj rx22ERMFYRXK1nU9QSA= =vy9R -----END PGP SIGNATURE----- --------------enigD1C2CB24E516ECCACA7E9B4B--