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 1LgNie-0005jy-D6 for garchives@archives.gentoo.org; Sun, 08 Mar 2009 18:27:24 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 07405E0756; Sun, 8 Mar 2009 18:27:23 +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 ABD4FE0756 for ; Sun, 8 Mar 2009 18:27:22 +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 BB31A16B1549 for ; Sun, 8 Mar 2009 19:27:21 +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: <20090308170104.GH14240@comet> References: <1236498557.6854.51.camel@neuromancer> <20090308164228.GG14240@comet> <20090308164806.1d3fa1d7@snowcone> <20090308170104.GH14240@comet> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-YrdGQNp1uZmYKf2GkGlT" Organization: Gentoo Date: Sun, 08 Mar 2009 19:27:04 +0100 Message-Id: <1236536824.9458.66.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: 59af66ed-7b12-4bbc-b2c6-9148a3b99dc2 X-Archives-Hash: a67e5904cc0b623a5d5bcb8e98acfc47 --=-YrdGQNp1uZmYKf2GkGlT Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Am Sonntag, den 08.03.2009, 10:01 -0700 schrieb Donnie Berkholz: > 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 how=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 >=20 The above could be rewritten to: ECONF_USE_WITH=3D"'x X' 'foo libfoo' 'bar' 'python pygtk'" econf $(use_with ${ECONF_USE_WITH}) or an eclass could even export this: src_configure() { [ -n ${ECONF_USE_WITH} ] && USE_WITH=3D"$(use_with \"${ECONF_USE_WITH}\")" econf ${USE_WITH} } Guessing from what I see in the gnome/kde eclasses I think people will implement the above then in eclasses and I therefore don't see why we can't do it like that from the beginning... (Besides, there are already shortcuts in eclasses like G2CONF=3D"...") --=-YrdGQNp1uZmYKf2GkGlT 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) iEYEABECAAYFAkm0DfgACgkQGwVqY66cHjB0vQCcCTVW+Y09WF4ntAb8kVLitu9e AygAn0T0Gk5W3AbL5bUTeLJR5mf/XX8x =/WHR -----END PGP SIGNATURE----- --=-YrdGQNp1uZmYKf2GkGlT--