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 1LgEXB-0000A5-Gy for garchives@archives.gentoo.org; Sun, 08 Mar 2009 08:38:57 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B4522E0609; Sun, 8 Mar 2009 08:38:55 +0000 (UTC) Received: from mail-ew0-f173.google.com (mail-ew0-f173.google.com [209.85.219.173]) by pigeon.gentoo.org (Postfix) with ESMTP id 54045E0609 for ; Sun, 8 Mar 2009 08:38:55 +0000 (UTC) Received: by ewy21 with SMTP id 21so462002ewy.34 for ; Sun, 08 Mar 2009 00:38:54 -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=ijC7PsArTCh9VpinXLn6AA0HoOnI64366SpDDIBrDd8=; b=QXPqV52ySpklAbPQQpY0YIv0FREYGFLpr+PZVm+wJZhbECZ5BD7XtdMZ2YYPvCL4M0 TEV9WeXgPM9wbXcLdCXrPAVX5jsnyftxK2oe9yfqVUMZWD0BmOeuilqJ8f8FLn0x2kC6 BV6EBwNhErvCSv9oAbFVUoBG8gUu9Lam6mhC4= 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=g6Zb9RbgxCIDTKY0GS2tf3GUzY+F4sDt1do730ps6n1qY6aJMGHdD3DLLyKtOb1YXj h/za56abVFpuZg7Ps6Ap4GGcChwWlA5ZmdbYMUweLr3ut2J1zW7bF7MCy3vw5eGd1ueq sQOckKBoOjOsaYLLllzBO496jCWhbIZCT80Q8= Received: by 10.210.65.15 with SMTP id n15mr1426005eba.94.1236501534613; Sun, 08 Mar 2009 00:38:54 -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 f6sm5327857nfh.0.2009.03.08.00.38.53 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 08 Mar 2009 00:38:54 -0800 (PST) Date: Sun, 8 Mar 2009 08:38:46 +0000 From: Ciaran McCreesh To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Ideas for a (fast) EAPI=3 Message-ID: <20090308083846.7d341909@snowcone> In-Reply-To: <49B37D05.50206@gentoo.org> References: <1236498557.6854.51.camel@neuromancer> <49B37D05.50206@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_/13uberstrJIbQ5hpgy9F3Ys"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Archives-Salt: 8d5efe70-acd1-447c-b816-a549500e85a6 X-Archives-Hash: 4b2d8e11cb80aba847b8ab687ab5af47 --Sig_/13uberstrJIbQ5hpgy9F3Ys Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 08 Mar 2009 00:08:37 -0800 Josh Saddler wrote: > Is there a reason why we should ram through a new EAPI for something > that *looks* like another "Paludis supports this so let's make it a > Portage standard" proposal? Is there some kind of time deadline here > that you all want? If we were sticking through "things Paludis has that're useful", the list would be an awful lot longer... And not everything on that list is even in Paludis... But hey, some things never go out of fashion. A few things on the list are required pretty soon. Bug 249166 and various existing screwups in the tree suggest that [use(+)] (or whatever syntax is decided upon) is going to crop up fairly frequently. And certain people are reluctant to nuke their prepalldocs calls despite Council decisions... I think the rest are just there because they're useful and easy. > Also, why the bannination of || ( foo? (.).) -- how is it error prone, > exactly. Last time I checked, every single use of foo? as a direct child of || in the tree was wrong, as were the Portage docs. Let's say you have the following: DEPEND=3D"|| ( foo? ( cat/foo ) bar? ( cat/bar ) cat/baz )" Then this is wrong: if use foo ; then myconf=3D"--enable-foo" elif use bar ; then myconf=3D"--enable-bar" else myconf=3D"--enable-baz fi Here's why: Say the user already has baz installed, and has USE=3D"foo". The package manager will see that baz is already installed, and as per the rules for || will not look at the foo or bar deps. So if the user doesn't have foo installed, the --enable-foo will be wrong. So the 'correct' code would have to be something like this: if use foo && has_version cat/foo ; then myconf=3D"--enable-foo" elif use bar && has_version cat/bar ; then myconf=3D"--enable-bar" else myconf=3D"--enable-baz fi Except this is *still* a mess, because a user who has USE=3D"foo bar" is going to end up with a differently configured package depending upon what he happens to have installed up-front, which is something that's not supposed to happen. --=20 Ciaran McCreesh --Sig_/13uberstrJIbQ5hpgy9F3Ys Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmzhBkACgkQ96zL6DUtXhF6RACgywkGN2AN6jv6Wf6ptjKy+e7s adkAn1u9jxvaysYtWV2QX/YUiRh/0kXk =di9v -----END PGP SIGNATURE----- --Sig_/13uberstrJIbQ5hpgy9F3Ys--