On Fri, 2009-02-27 at 12:31 -0800, Dan Nicholson wrote:
> > I was trying to do this (for hv3...) and couldn't figure out a way.
> > Mandriva can do it, because its %configure script includes a
> > CONFIGURE_TOP variable:
> >
> > # This is an improved version of %configure (from PLD team).
> > %configure \
> > %before_configure ; \
> > %{?!_disable_libtoolize:%{?__libtoolize_configure:%{__libtoolize_configure};}} \
> > [ -f $CONFIGURE_TOP/configure.in -o -f $CONFIGURE_TOP/configure.ac ] && \
> > CONFIGURE_XPATH="--x-includes=%{_prefix}/include --x-libraries=%{_prefix}/%{_lib}" \
> > $CONFIGURE_TOP/configure %{_target_platform} \\\
> >
> > (etc etc etc)
> >
> > might be nice to have that in Fedora. Obviously, if CONFIGURE_TOP is not
> > specified it defaults to ./ , and if you want to run a configure from
> > some other dir, you define CONFIGURE_TOP in the spec.
>
> Would it not be more appropriate to do this as a macro? It seems like
> CONFIGURE_TOP is an environment variable.
>
> rpm/macros:
> %_configure ./configure
> %configure \
> %{_configure} ...
>
> And then
>
> %define _configure ../configure
> cd build
> %configure --enable-other-stuff
Sure, looks sensible to me. I think the CONFIGURE_TOP stuff is quite
old, it may have been a different scenario back when it was invented.
macro looks like a good way to do it now.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
