From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 9B589138010 for ; Thu, 30 Aug 2012 19:47:16 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 279BEE0417; Thu, 30 Aug 2012 19:46:35 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id EADDBE01C9 for ; Thu, 30 Aug 2012 19:45:00 +0000 (UTC) Received: from [192.168.178.20] (p548D2D0D.dip.t-dialin.net [84.141.45.13]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: tommy) by smtp.gentoo.org (Postfix) with ESMTPSA id 472FB33D90A for ; Thu, 30 Aug 2012 19:44:59 +0000 (UTC) Message-ID: <503FC2B2.4090103@gentoo.org> Date: Thu, 30 Aug 2012 21:44:50 +0200 From: Thomas Sachau User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120721 Firefox/14.0.1 SeaMonkey/2.11 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 References: <1650487.RNHkTcOSMI@elia> <503F477B.2050507@gentoo.org> <201208301527.07308.dilfridge@gentoo.org> In-Reply-To: <201208301527.07308.dilfridge@gentoo.org> X-Enigmail-Version: 1.5a1pre OpenPGP: id=211CA2D4 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigB668EBD3BC8425986DBDD8C3" X-Archives-Salt: 6ddd1953-6d4d-4805-9853-4f2ffa0d7411 X-Archives-Hash: b09b75c648228d07ca415fb34e571019 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB668EBD3BC8425986DBDD8C3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Andreas K. Huettel schrieb: > Am Donnerstag, 30. August 2012, 12:59:07 schrieb hasufell: >> Could you elaborate what the reasons FOR it are (not that I don't know= >> any, but you brought it up) since this will add work for every develop= er >> to check a) how the behavior of the new EAPI impacts the current ebuil= d >> and b) how the behvaior of inherited eclasses change depending on EAPI= =2E >=20 > a) Easier eclass maintenance.=20 > Restricting the kde4 eclasses to EAPI 3 and 4 made the code indeed simp= ler.=20 > We'll raise that to 4 only soon (after fixing the remaining ebuilds in = the=20 > tree.) An eclass, which includes helper commands like eutils or versionator eclass wont benefit from it. Only specific eclasses (like your kde example would benefit and for those, the related team can always decide to bump all their packages to the wanted EAPI and then to bump the eclass requirement. So no need to force this on everyone else. >=20 > b) Easier overall tree maintenance. > I've recently removed a useflag on poppler (xpdf-headers for those=20 > interested). Of course, this involved fixing all in-tree reverse depend= encies=20 > first. Now I consider myself very lucky there, because all except two p= ackages=20 > were EAPI 4 and I could use (+). One package was EAPI 3 and I unceremon= iously=20 > bumped it to 4. One was EAPI 0. Having fun with || there.=20 If a package has a maintainer, you could just ask him to fix the issue, so you dont have to even think about the EAPI. And if there is no maintainer, you can take and bump it. And if noone wants to maintain it, it will be dropped at some point. So you can bump whatever you maintain, just still the question: Why force this on everyone else? --=20 Thomas Sachau Gentoo Linux Developer --------------enigB668EBD3BC8425986DBDD8C3 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.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iJwEAQECAAYFAlA/wrcACgkQG7kqcTWJkGczuAP/Zj3WofqIh8uYxH4Qm1FEaTH8 nD+yuJK8gOWwArNanPUqtaQed0Xk6S943LsvrMmZg/F6Cojt/4v93VzUULy02nLJ 0K6my3vdvUY+5TuCYhBZeHwD9BxSb5kSK8SxOw/SkUx75clTTFV9GdHbQbmOUsn9 0gtMN68UdDR5J62b3J4= =aOC3 -----END PGP SIGNATURE----- --------------enigB668EBD3BC8425986DBDD8C3--