Hello Paul,
* Paul Eggert wrote on Wed, Jan 23, 2008 at 12:54:50AM CET:
> Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>
> > +that creates @file{install} from it if there is no makefile. Starting with
> > +Autoconf 2.62, this macro requires @command{install} to be able to install
> > +multiple files into a target directory.
>
> A minor point: as a general rule, it's better not to put version
> numbers into the manual like that, as it clutters up the manual
> unnecessarily. Information about when features were added is best
> left in NEWS. There are sometimes exceptions to that general rule
> (incompatible changes come to mind), but this isn't one of them.
OK with me, I've applied the patch below.
> Thanks for the rest of the change, by the way, it's a nice one.
My pleasure. It should lead to greatly reduced `make install' times.
Cheers,
Ralf
* doc/autoconf.texi (Particular Programs): Do not mention the
Autoconf version in which the AC_PROG_INSTALL change was done.
Suggested by Paul Eggert.
diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index 4e32e08..78628e5 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -3730,9 +3730,9 @@ This macro screens out various instances of
@command{install} known not to
work. It prefers to find a C program rather than a shell script, for
speed. Instead of @file{install-sh}, it can also use @file{install.sh},
but that name is obsolete because some @command{make} programs have a rule
-that creates @file{install} from it if there is no makefile. Starting with
-Autoconf 2.62, this macro requires @command{install} to be able to install
-multiple files into a target directory in a single invocation.
+that creates @file{install} from it if there is no makefile. Further, this
+macro requires @command{install} to be able to install multiple files into a
+target directory in a single invocation.
Autoconf comes with a copy of @file{install-sh} that you can use. If
you use @code{AC_PROG_INSTALL}, you must include either
