On 2003-07-03(Thu) 08:22:12 +0200, Michael Scherer wrote:
> > But Charles, upgrading to 1.5 can mean a lot of trouble too. Yes,
> > sooner or later we will move on, but for now, you have do these steps
> > when building stuff with libtool 1.5, if software was bundling
> > libtool 1.4:
> >
> > %{_libtoolize} -c -f
> > aclocal
> > autoconf
>
> maybe i am saying something dump, but, what about adding these steps to
> the %configure macro ?I would have suggested it if it's possible. But you will see such variants when executing aclocal and autoconf: aclocal-1.7 aclocal-1.4 aclocal -I /usr/share/aclocal/something WANT_AUTOCONF_2_5=1 autoconf WANT_AUTOCONF_2_1=1 autoconf Everything can be different on each package. Sometimes different automake and autoheader calls may be inserted in between too. But note that if the software is already bundling libtool 1.5, then nothing other than libtoolize is needed. I want to grind autotool maintainers into powder. :) Abel > Of course, the whole process of rebuilding will be slower. This is not > much, but, for each package, this can be significant. > > -- > > Mickaël Scherer > > -- Abel Cheung Linux counter #256983 | http://counter.li.org GPG Key: (0xC67186FF) | http://deaddog.org/gpg.asc Key fingerprint: 671C C7AE EFB5 110C D6D1 41EE 4152 E1F1 C671 86FF
pgp00000.pgp
Description: PGP signature
