Re: libtool and autoconf

[Alexander Mai]

On Mon, 3 Sep 2001 18:48:09 +0100, Gary V. Vaughan wrote:

>On the contrary, NEWS is exactly the file users are supposed to read
>whenever you untar a new release.  It is after all a list of "user
>visible changes since the last release".
[...]
>> To repeat myself: I don't think that any GNU or whatever
>> standard forces people to read a ChangeLog/NEWS or whatever
>> files which are usually just for 'insiders' to follow
>> development? Why should a new user to libtool care
>> about it's history?
>
>Agreed in the case of ChangeLog.  But if you are upgrading from one
>release of libtool to another, why _wouldn't_ you want to know what
>has changed?

Yes.
But I'm stubborn and still believe that all information
of this kind should be in my printouts. And I neither do have
nor even want to have a NEWS.ps ... :-)

>> Does this mean that there won't be anything
>> beyond 1.4 which is happy with autoconf 2.13?
>
>Pretty much.  Alpha releases leading to libtool-1.5 (and beyond) will
>definitely need recent autoconf and automake releases, but I'll accept
>patches to make libtool.m4 and ltdl.m4 useful for projects that won't
>(or can't) upgrade -- if some one else has the time to put the work in.

Well, seems that 1.4.1 might even cure my current problems!
I don't see it anymore, but I sometimes already got problems
when just switching to a new version, I should re-check after
removing all related stuff.

autoconf 2.5x is not a choice for many users.
There's too much legacy stuff (.in/.m4) out there that
can't be used. This won't change for a long time ...
I probably can't supply fixes, but will keep on
reporting problems with my autoconf 2.13/libtool 1.4.x setup -
if there are any :-)

Bye,


---
Alexander Mai
address@hidden