Re: libtool and autoconf

[Gary V. Vaughan]

On Mon, Sep 03, 2001 at 08:37:46PM +0200, Alexander Mai wrote:
> 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 ... :-)

I see.  Could I talk you into reading the release notes in each
release announcement?  Paraphrased in:

    http://www.gnu.org/software/libtool/news.html
    
??

> 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 :-)

Okay, thanks.  I definitely want to keep Libtool 1.4.x compatible with
Autoconf 2.13.  I imagine libtool 1.5 may be as much as 12 months
away, so autotools users will have had almost 2 years to absorb the
excellent advances made in Autoconf 2.5x...

Cheers,
        Gary.
-- 
  ())_. Gary V. Vaughan     gary@(oranda.demon.co.uk|gnu.org)
  ( '/  Research Scientist  http://www.oranda.demon.co.uk       ,_())____
  / )=  GNU Hacker          http://www.gnu.org/software/libtool  \'      `&
`(_~)_  Tech' Author        http://sources.redhat.com/autobook   =`---d__/