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 1K6Q4S-0004H0-Ne for garchives@archives.gentoo.org; Wed, 11 Jun 2008 13:09:00 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0C059E0555; Wed, 11 Jun 2008 13:08:37 +0000 (UTC) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by pigeon.gentoo.org (Postfix) with ESMTP id 856B2E0555 for ; Wed, 11 Jun 2008 13:08:36 +0000 (UTC) Received: by py-out-1112.google.com with SMTP id w53so1362466pyg.25 for ; Wed, 11 Jun 2008 06:08:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=IUSrEuPvCY7M/GePS1leQLxN7jgQoY3lb2eQ31Q5Yoc=; b=UiwhuIfafkxMfHq3fXRo05UTREfVt41yjKQmHQG2FPhH1Yd6QlOig3oIifRSZjfkgS jQ6rEoU0D+z91H26gKepq7wvug0G0XTebiXcq/XvxE5XqzbRVdOoOfyhcU9mSrI6MWEA xMJlqBepLrLp558taoWmQWGchp/sGje8Q5tVE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=bebsYbQ8jruL+EQexbnDZBzf0eR1kATOKHqr7kuA+SGouGUSrTXJMqpTygZioXyLcG su92n9xHC+W3rKtK03oXLgMXPgle4yr29ktZnKHNXrWQRIcxmJYUY5PRqkE9lds6v4Jr yPjMCJBEj/8CaVKVJ1FlxNPuKpDbjpBMAU/fE= Received: by 10.115.14.1 with SMTP id r1mr6473791wai.139.1213189715137; Wed, 11 Jun 2008 06:08:35 -0700 (PDT) Received: from seldon ( [98.210.154.155]) by mx.google.com with ESMTPS id m10sm21627612waf.59.2008.06.11.06.08.32 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 11 Jun 2008 06:08:34 -0700 (PDT) Date: Wed, 11 Jun 2008 06:08:20 -0700 From: Brian Harring To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] EAPI-2 - Let's get it started Message-ID: <20080611130820.GA10492@seldon.metaweb.com> References: <20080611001123.GA7972@seldon.metaweb.com> <20080611065737.3ac6cfb6@googlemail.com> <484F6A88.6090404@gentoo.org> <20080611071121.6082e3e2@googlemail.com> <484FAF31.10901@gentoo.org> <20080611121438.1ab87917@googlemail.com> <484FBF75.1030502@gentoo.org> <484FC764.2060409@bernd-steinhauser.de> <484FC9CF.6010708@gentoo.org> <20080611140019.0b7a9fe2@googlemail.com> 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 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+HP7ph2BbKc20aGI" Content-Disposition: inline In-Reply-To: <20080611140019.0b7a9fe2@googlemail.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Archives-Salt: e923762d-4654-4578-9ab2-856742243eb2 X-Archives-Hash: 38e22d42c8ad12ad99b0e16145af44e2 --+HP7ph2BbKc20aGI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 11, 2008 at 02:00:19PM +0100, Ciaran McCreesh wrote: > On Wed, 11 Jun 2008 14:49:19 +0200 > Luca Barbato wrote: > > > Why is "Create tests for EAPI=3D1 stuff." not a way to describe how > > > to reproduce a problem? > >=20 > > because EAPI1 isn't specified completely so you don't have a large > > field to cover but you also do not know the bounds of it. >=20 > EAPI 1 is entirely specified in terms of a diff against EAPI 0. > Checking every part that's changed before releasing an EAPI 1 package > manager is the least any responsible person would do. That they would > release a version without doing such basic tests shows you just how > much they care about Gentoo... >=20 > > Assuming that Ciaranm isn't just lying knowingly it's just plainly > > rude, otherwise it is pure malice. >=20 > What, asking the pkgcore people to test their code before releasing a > version that claims to support EAPI 1 but actually doesn't, forcing > people to avoid using some of EAPI 1 to avoid breaking pkgcore, is > malice? >=20 > The whole "EAPI lets us do upgrades cleanly" process is broken when > people release a package manager that claims to support a certain EAPI > but doesn't. If pkgcore had any actual users we'd have to consider > banning EAPI 1 in the tree and releasing EAPI 2 as being identical to > EAPI 1 just to work around this. Ya know ciaran, I've just got to point out that you spend quite a=20 large amount of time talking about pkgcore. Literaly- you talk about=20 it more then I do. I could point out how paludis (or portage) has picked up the misc=20 functionality pkgcore (then known as saviour, or ebd) established 4=20 years back, but hey, I'm not petty like you. Generators aren't at all=20 like the basic repository concept, no sir. But you know that, of=20 course, and of course you've got nothing to worry about from pkgcore,=20 no sir. Alternatively, I'll take your tack- eapi1 actually isn't supported by=20 paludis. Ask me what bug, please, trust me I'll make it entertaining=20 for the gentoo-dev readers. ~harring --+HP7ph2BbKc20aGI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFIT85DsiLx3HvNzgcRAm2TAJ978MBcVA5TUUGLGDlk0C4IsrYGnQCZAWG5 a/vWEjOWB9u4/fG5tJX2GpE= =ytPz -----END PGP SIGNATURE----- --+HP7ph2BbKc20aGI-- -- gentoo-dev@lists.gentoo.org mailing list