On Apr 1, 2000, Erez Zadok <[EMAIL PROTECTED]> wrote:
> and I cannot make dist. I realize why it was done, but I like to be
> able to make my own custom distributions which I unpack on remote
> machines for testing.
I'd rather be safe and avoid ever creating a libtool tarball without
uncommitted changes in ChangeLog, because that's our main
version-control mechanism. You can always run `make dist CVS=:', that
should avoid the problem for you, or install the patch you suggest.
> (2) The config.{sub,guess} distributed in libtool CVS tree are rather old.
> The "common" GNU cvs package is gone. Instead, the newer files are
> distributed from ftp://ftp.gnu.org/pub/gnu/config/
They're usually only upgraded just before a release. There's not much
point in trying to keep them in sync with the master repo. Is there
any particular reason why you think we should upgrade it now, rather
than at release time?
> (3) when running bootstrap, using the latest autoconf/automake, I get
> several of these errors:
Akim is reportedly working on making autoconf more friendly to
``out-of-date'' `configure.in's. Our (my?) intention is to keep
libtool compatible with old versions of autoconf and automake for as
long as possible, so I'd rather not modify configure.in just to
silence these warnings, if this means breaking compatibility with
older auto* tools.
> Making the changes to libtol is pretty simple. I can make them and submit a
> patch if you'd like.
Thanks anyway :-)
--
Alexandre Oliva Enjoy Guaranį, see http://www.ic.unicamp.br/~oliva/
Cygnus Solutions, a Red Hat company aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org} Write to mailing lists, not to me
