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 1LcMDn-0000R3-P4 for garchives@archives.gentoo.org; Wed, 25 Feb 2009 16:02:56 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 298C9E07C7; Wed, 25 Feb 2009 16:02:38 +0000 (UTC) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by pigeon.gentoo.org (Postfix) with ESMTP id BEA79E07C7 for ; Wed, 25 Feb 2009 16:02:37 +0000 (UTC) Received: by nf-out-0910.google.com with SMTP id d3so35730nfc.26 for ; Wed, 25 Feb 2009 08:02:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:in-reply-to:references:x-mailer:mime-version :content-type; bh=ZwYH8Rz4oS46VSe7kRYP53Kq8cWA/MFHdpeW4sRzauU=; b=fQGZ+GDSs6GC5dhIped4qpGDIyzL0xOWi4O7iq3UVANo4tUzC5S9L6AZiXZaJHdTpo h9Wd+qHiLK41fbhZphC2i8buHnY2nM0T0v8t9Vv29XUHG6wQaSBpmqTYsWvab+tGY9Th Cotzm/pIbu71K0vVucPaei3dQciW9J3RS+lT4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type; b=d4iwAoTQscnnCG80Mg29wAEcjA3C/Z6WFffmdciempOyWNeOWK6qaa5aL1nmiHhJY/ HP0qtu1Y3McodrtE8hidvIvAjam6gJSJejohVZBGLbViyVjyTXtRhgY81OlbZZQMHid5 UDfRuhGYDjB2BiDUHB/8mZtsKbckDqptuoFe4= Received: by 10.210.21.6 with SMTP id 6mr189001ebu.38.1235577757055; Wed, 25 Feb 2009 08:02:37 -0800 (PST) Received: from snowcone (92-235-187-79.cable.ubr18.sgyl.blueyonder.co.uk [92.235.187.79]) by mx.google.com with ESMTPS id 10sm129206eyd.53.2009.02.25.08.02.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 25 Feb 2009 08:02:36 -0800 (PST) Date: Wed, 25 Feb 2009 16:02:28 +0000 From: Ciaran McCreesh To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Issues regarding glep-55 (Was: [gentoo-council] Re: Preliminary Meeting-Topics for 12 February 2009) Message-ID: <20090225160228.45e4eb25@snowcone> In-Reply-To: <49A56A14.2080400@gentoo.org> References: <1234257125.18160.2016.camel@localhost> <1234450419.20950.2.camel@localhost> <20090212160045.GB3642@comet> <20090212161644.GD3642@comet> <20090212162103.256b003f@snowcone> <20090212171055.GA3652@comet> <20090212172109.778fb268@snowcone> <20090212173743.GD3652@comet> <20090212180350.0d9a9df5@snowcone> <1235037961.13198.779.camel@localhost> <20090219125124.33eaa66c@snowcone> <1235077892.13198.1923.camel@localhost> <20090222171658.278ae167@halo.dirtyepic.sk.ca> <49A1E1CB.1000806@gentoo.org> <20090222234800.29d64b8d@snowcone> <49A206A7.3050604@gentoo.org> <49A39CE7.4010201@gentoo.org> <20090224141912.0a666a17@snowcone> <49A41A8C.1060002@gentoo.org> <20090224161449.07bc580a@snowcone> <49A42B86.9010903@gentoo.org> <20090224182416.3db4f60f@snowcone> <49A4B54E.4060202@gentoo.org> <20090225153347.3e9aaafa@snowcone> <49A56A14.2080400@gentoo.org> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; x86_64-pc-linux-gnu) 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; boundary="Sig_//wbvAH2xJkVLoZ6LyS.5BKs"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Archives-Salt: 13645340-f64e-47fb-944a-1d874decb390 X-Archives-Hash: 3fdfd54327346a1900677766ae48cf1e --Sig_//wbvAH2xJkVLoZ6LyS.5BKs Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 25 Feb 2009 16:56:04 +0100 Luca Barbato wrote: > > That you're bringing ebuild.sh into this shows you still haven't > > worked out how the process works. There is no need to use ebuild.sh > > (which is a very good thing, because launching bash is > > slooooooooooooow) when there's valid metadata. >=20 > it there is a valid metadata you have everything there already and > you don't have to parse the ebuild so... Except you can't tell whether the metadata is valid unless you already know the EAPI. As you have already been told. > >>> So you have patches for Portage? Please show them. > >> Up there what's enough to check the viability for the solution. > >=20 > > No, it's completely wrong. ebuild.sh has nothing to do with this. >=20 > Is there another place in portage that extracts the EAPI value? Yup. The part where it reads the metadata cache. > > Yes, it will warn noisily. This is unacceptable, since stable users > > will have months and months of noise when new rules come along. >=20 > "unacceptable"... >=20 > as in "it's ugly to see"... No, as in it'll result in zillions of users wondering what's going on and why their screen is getting spammed, and zillions of bug reports and forum posts. --=20 Ciaran McCreesh --Sig_//wbvAH2xJkVLoZ6LyS.5BKs Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmla5cACgkQ96zL6DUtXhHHZgCgzhWJGJbdQUhU/Ku0oj1kU32g tkoAoLM07FUR8vfd7GtahvlAMrPbVYsR =56N9 -----END PGP SIGNATURE----- --Sig_//wbvAH2xJkVLoZ6LyS.5BKs--