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 1KpsTd-0002CN-QZ for garchives@archives.gentoo.org; Tue, 14 Oct 2008 22:34:55 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7284DE03F3; Tue, 14 Oct 2008 22:34:53 +0000 (UTC) Received: from smtp03.tky.fi (smtp03.tky.fi [82.130.63.73]) by pigeon.gentoo.org (Postfix) with SMTP id 2AFCEE03F3 for ; Tue, 14 Oct 2008 22:34:53 +0000 (UTC) Received: from [82.130.46.209] ([82.130.46.209]) by smtp03.tky.fi (SMSSMTP 4.1.9.35) with SMTP id M2008101501344902014 for ; Wed, 15 Oct 2008 01:34:49 +0300 Message-ID: <48F51E8B.9000600@gentoo.org> Date: Wed, 15 Oct 2008 01:34:51 +0300 From: =?UTF-8?B?UGV0dGVyaSBSw6R0eQ==?= User-Agent: Thunderbird 2.0.0.17 (X11/20081003) 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] Stabilize ebuilds which use EAPIs only supported by ~arch PMs References: <20081014000340.GA5494@gentoo.org> <20081014003834.GE23706@comet> <20081014085939.GA5520@gentoo.org> <20081014181712.1a5ad3c7@sheridan.genone.homeip.net> In-Reply-To: <20081014181712.1a5ad3c7@sheridan.genone.homeip.net> X-Enigmail-Version: 0.95.7 OpenPGP: url=http://users.tkk.fi/~praty/public.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0A0EE2C5FCAD1AA3A546C6FA" X-Archives-Salt: 75702e8a-af06-4d4b-9ec3-45fa82f438d4 X-Archives-Hash: 10fda85cefb940dd84c01d3ed0fbbe0f This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0A0EE2C5FCAD1AA3A546C6FA Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Marius Mauch kirjoitti: > On Tue, 14 Oct 2008 10:59:39 +0200 > Jose Luis Rivero wrote: >=20 >> On Mon, Oct 13, 2008 at 05:38:34PM -0700, Donnie Berkholz wrote: >>> On 02:03 Tue 14 Oct , Jose Luis Rivero wrote: >>>> There are some others sceneries but are not so common as the one >>>> presented could be. Any decent solution for this case? >>> There are only a few obvious ones, you'll have to pick which one >>> you like best. Most of the other options basically duplicate these >>> in some way or add more work to them for negligible gain: >>> >>> - Backport the ebuild from EAPI=3D2 to EAPI=3D0 >> EAPI-2 to EAPI-0 could imply lot of changes (not talking about what is= >> going to happen when we release new and more feature rich EAPIs), and >> changes usually come with bugs. The ebuild is committed directly to >> stable implies bugs in stable, which for me is a no-go. >=20 > Assuming the ebuild changes between foo-1 and foo-2 are mainly due to > the change from EAPI=3D0 to EAPI=3D2 (which I'd expect to be true in ma= ny > cases) you could just reuse the foo-1 ebuild for foo-3. >=20 > If there are major differences between foo-1 and foo-2 not related to > the EAPI change then the maintainer probably didn't want foo-2 to > become stable anytime soon, so it's at least questionable if foo-3 > should go straight to stable in the first place. >=20 > And adding a new version directly to stable always comes with a risk, > you can't eliminate that completely. It's all about risk assessment, > and how much work you're willing to do or time you want to spend to > minimize the risk. >=20 There's no need to commit straight to stable. Just make two different new revisions for each EAPI. Then the arch teams can test it like usual. Regards, Petteri --------------enig0A0EE2C5FCAD1AA3A546C6FA 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.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkj1Ho8ACgkQcxLzpIGCsLRh8ACeMNcJLd3l+tHzfcxSadoirW/5 JNMAnApRSdj8OP8ov2R3p9UuYwW6bQBS =TXNL -----END PGP SIGNATURE----- --------------enig0A0EE2C5FCAD1AA3A546C6FA--