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 1LgNqx-0006cR-2X for garchives@archives.gentoo.org; Sun, 08 Mar 2009 18:35:59 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1F90EE077F; Sun, 8 Mar 2009 18:35:58 +0000 (UTC) Received: from smtp.tmcs.ch (113.245.131.213.static.inetbone.net [213.131.245.113]) by pigeon.gentoo.org (Postfix) with ESMTP id C37C9E077F for ; Sun, 8 Mar 2009 18:35:57 +0000 (UTC) Received: from [192.168.0.100] (121-180.3-85.cust.bluewin.ch [85.3.180.121]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.tmcs.ch (Postfix) with ESMTPSA id 80C4416B1B89 for ; Sun, 8 Mar 2009 19:35:56 +0100 (CET) Subject: Re: [gentoo-dev] Ideas for a (fast) EAPI=3 From: Tiziano =?ISO-8859-1?Q?M=FCller?= To: gentoo-dev@lists.gentoo.org In-Reply-To: <20090308182446.GI14240@comet> References: <1236498557.6854.51.camel@neuromancer> <20090308164228.GG14240@comet> <20090308164806.1d3fa1d7@snowcone> <20090308170104.GH14240@comet> <20090308182446.GI14240@comet> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-Z4DNd7wPzDfr/KVjYEzp" Organization: Gentoo Date: Sun, 08 Mar 2009 19:35:39 +0100 Message-Id: <1236537339.9458.74.camel@neuromancer> 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 X-Mailer: Evolution 2.24.5 X-Archives-Salt: d2fc70c5-6450-48e2-b04c-84a202d4f8b9 X-Archives-Hash: f8af4434923d8ff4c3f68fd74c988777 --=-Z4DNd7wPzDfr/KVjYEzp Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Am Sonntag, den 08.03.2009, 11:24 -0700 schrieb Donnie Berkholz: > On 10:01 Sun 08 Mar , Donnie Berkholz wrote: > > On 16:48 Sun 08 Mar , Ciaran McCreesh wrote: > > > On Sun, 8 Mar 2009 09:42:29 -0700 > > > Donnie Berkholz wrote: > > > > - I understand the reasoning for the SRC_CONFIGURE_WITH blah stuff.= I=20 > > > > strongly oppose this implementation because it makes ebuilds less > > > > like bash scripts that are easy to understand. Instead I suggest > > > > extending use_with() and use_enable() to accept multiple sets of > > > > arguments (alternately, making custom, similar functions that will > > > > take multiple args). > > >=20 > > > How would that work? I can't see an obvious way of doing it that isn'= t > > > more or less as verbose as just using multiple calls. > >=20 > > It would just eliminate all but one call to use_with(). Depending on ho= w=20 > > many you've got, this can shorten things up a fair bit. Here's an=20 > > example: > >=20 > > econf \ > > $(use_with 'x X' 'foo libfoo' 'bar' 'python pygtk') > > econf \ > > $(use_with x X) \ > > $(use_with foo libfoo) \ > > $(use_with bar) \ > > $(use_with python pygtk) >=20 > And the straightforward evolution of this would be additional with() and=20 > enable() functions for mandatory support. I still find this more=20 > intuitive than the set of variables. >=20 > econf \ > $(use_with 'x X' 'foo libfoo' 'bar' 'python pygtk') \ > $(with foo bar blah baz) \ > $(enable bam paw tick) >=20 Which could already be written as ... econf --with-{foo,bar} using bash :-) (or did I miss the point?) --=-Z4DNd7wPzDfr/KVjYEzp Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Dies ist ein digital signierter Nachrichtenteil -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (GNU/Linux) iEYEABECAAYFAkm0D/sACgkQGwVqY66cHjDBKgCfVXDeekF5KkKsMKyOD989rYOB OYQAn2NrdotUGpxHW2pHTenHr2s/rGKd =3Z5r -----END PGP SIGNATURE----- --=-Z4DNd7wPzDfr/KVjYEzp--