Re: obsolete and/or redundant files in Automake CVS?

[Alexandre Duret-Lutz]

>>> "Paul" == Paul Eggert <address@hidden> writes:

 Paul> In looking at the latest Automake CVS I noticed that ./install-sh is
 Paul> obsolete (as compared to Autoconf 2.54).  Does that file need to be
 Paul> distributed any more?  lib/install-sh is up-to-date and it seems to me
 Paul> that ./install-sh should not be needed any more.

 Paul> A similar situation occurs with mkinstalldirs vs lib/mkinstalldirs,
 Paul> and with mdate-sh vs lib/mdate-sh.

 Paul> Slightly different is the case of ./missing vs lib/missing; in this
 Paul> case the files are identical but surely ./missing is redundant.

The copies in ./ are the files used during the build.  lib/ are
the files used by `automake -a'.  AFAICT we can't merge both
directories because `automake -a' would overwrite its own files.

lib/ is the master location of these files, most of them are
updated by `make fetch' before we make a release.  Maybe a
simple fix would be to have a `install-sh: lib/install-sh' rule
to make sure these files are up-to-date.

 Paul> I also noticed that the following files seem to be obsolete compared
 Paul> to Autoconf 2.54.  I assume they're supposed to be identical.

 Paul> lib/Automake/General.pm
 Paul> lib/Automake/Struct.pm
 Paul> lib/Automake/XFile.pm (the only difference is Automake vs Autom4te?)
 Paul> INSTALL

XFile.pm and lib/INSTALL are updated from Autoconf by `make
fetch' (which changes Autom4te as Automake).  We could do the
same for others, although General.pm carries and export too many
unrelated things that Automake doesn't use -- I've long wanted
to split this file.
-- 
Alexandre Duret-Lutz