Re: build-aux-update: wget vs libtoolize

[Sam S. <sd...@gn...>]

Bruno,

Bruno Haible wrote:
> 
>> why did you decide to use wget libtool tarball + cp instead of libtoolize for
>> updating clisp libtool files?
> 
> It is important to get ltmain.sh and libtool.m4 together.
> In version 1.5.x of libtool, "libtoolize" installed only the ltmain.sh, *not*
> the .m4 macros. Then you created a tarball from that, copied it to another
> machine or distributed it to someone else. Then, after running 'aclocal' and
> 'autoconf', the user had a configure file that did not match the version of
> ltmain.sh that he had. Leading to weird errors.

thanks. the only missing information in the comment was that it was a bug in 
libtoolize 1.5.

> This bug is fixed in libtool 2.x. So, you can now change the commands to use
> "./configure --prefix=$tmpdir && make && make install && $tmpdir/bin/libtoolize"
> instead of the "cp" commands.

why not just check that the system-wide installation is newer than the libtool 
which already comes with clisp and use it?
the only problem is that there is no function which would correctly compare 
1.5.22 with 2.2.8

> But I would continue to specify a certain, fixed, version of libtool in
> Makefile.devel. Otherwise different clisp testers end up using different
> versions of libtool, which does really help when problems occur.

huh? the only people who ever do this are the maintainers.

Sam.