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 <dberkh...@gentoo.org> wrote: > > > - I understand the reasoning for the SRC_CONFIGURE_WITH blah stuff. I > > > 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). > > > > 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. > > It would just eliminate all but one call to use_with(). Depending on how > many you've got, this can shorten things up a fair bit. Here's an > example: > > 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) > >
The above could be rewritten to:
ECONF_USE_WITH="'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="$(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="...")
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
