From: Alexandre Duret-Lutz Date: Sun, 23 Feb 2003 18:51:58 +0000 (+0000) Subject: * automake.texi (FAQ, CVS, maintainer-mode, wildcards) X-Git-Tag: Release-1-7-3b~53 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b1ba945c3e62b53735595bce3a61a6bd075ecf68;p=thirdparty%2Fautomake.git * automake.texi (FAQ, CVS, maintainer-mode, wildcards) (distcleancheck): Fix typos and other errors reported by Karl Berry. --- diff --git a/ChangeLog b/ChangeLog index eafdc48e9..ea5f4c01d 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2003-02-23 Alexandre Duret-Lutz + + * automake.texi (FAQ, CVS, maintainer-mode, wildcards) + (distcleancheck): Fix typos and other errors reported by Karl + Berry. + 2003-02-20 Alexandre Duret-Lutz * lib/am/texibuild.am (%SOURCE_SUFFIX%%DEST_SUFFIX%): Use $(...) diff --git a/automake.texi b/automake.texi index bcef3742f..27dc0bd28 100644 --- a/automake.texi +++ b/automake.texi @@ -5412,7 +5412,7 @@ the test-suite. @node FAQ, Macro and Variable Index, API versioning, Top @chapter Frequently Asked Questions about Automake -This chapters covers some questions that often come up on the mailing +This chapter covers some questions that often come up on the mailing lists. @menu @@ -5566,7 +5566,7 @@ using (hence testing) their own generated files, instead of the generated files that will be released actually. The developer who prepares the tarball might be using a version of the tool that produces bogus output (for instance a non-portable C file), something -other developers could have noticed if they weren't using there own +other developers could have noticed if they weren't using their own versions of this tool. @subsection Third-party files @@ -5614,7 +5614,7 @@ development: developers love fixing failures. However, users with wrong versions of maintainer tools may get an error when the rebuild rule is spuriously triggered, halting the build. This failure to let the build continue is one of the arguments of the -@code{AM_MAINTAINER_MODE} advocators. +@code{AM_MAINTAINER_MODE} advocates. @subsection @code{AM_MAINTAINER_MODE} @cindex AM_MAINTAINER_MODE, purpose @@ -5643,7 +5643,7 @@ rules that need exotic tools that users may not have available. Several years ago François Pinard pointed out several arguments against @code{AM_MAINTAINER_MODE}. Most of them relate to insecurity. By removing dependencies you get non-dependable builds: change to -sources files can have no-effect on generated files and this can be +sources files can have no effect on generated files and this can be very confusing when unnoticed. He adds that security shouldn't be reserved to maintainers (what @code{--enable-maintainer-mode} suggests), on the contrary. If one user has to modify a @@ -5707,10 +5707,10 @@ Finally it's really hard to @file{forget} adding a file to compiled nor installed, so you can't even test it. @end itemize -Still, these are philosophic objections, and as such you may disagree, +Still, these are philosophical objections, and as such you may disagree, or find enough value in wildcards to dismiss all of them. Before you start writing a patch against Automake to teach it about wildcards, -let's see the the main technical issue: portability. +let's see the main technical issue: portability. Although @code{$(wildcard ...)} works with GNU @command{make}, it is not portable to other @command{make} implementations. @@ -5722,7 +5722,7 @@ list all files and not use @code{$(wildcard ...)}. However that means developers need to remember they must run @code{automake} each time they add, delete, or rename files. -Compared to editing @file{Makefile.am}, this really little win. Sure, +Compared to editing @file{Makefile.am}, this is really little win. Sure, it's easier and faster to type @code{automake; make} than to type @code{emacs Makefile.am; make}. But nobody bothered enough to write a patch add support for this syntax. Some people use scripts to @@ -5776,9 +5776,9 @@ proceed with an example. Suppose our package contains a program for which we want to build a man page using @command{help2man}. GNU @command{help2man} produces simple manual pages from the @code{--help} and @code{--version} output of other commands (@pxref{Top, , Overview, -help2man, The Help2man Manual}). Because we don't want our users to -install @command{help2man}, we decide to distribute the generated man -page using the following setup. +help2man, The Help2man Manual}). Because we don't to force want our +users to install @command{help2man}, we decide to distribute the +generated man page using the following setup. @example # This Makefile.am is bogus. @@ -5885,8 +5885,7 @@ For desperate cases, it's always possible to disable this check by setting @code{distcleancheck_listfiles} as documented in @ref{Dist}. Make sure you do understand the reason why @code{make distcheck} complains before you do this. @code{distcleancheck_listfiles} is a -way to @emph{hide} errors, not to fix them. There is always better to -do. +way to @emph{hide} errors, not to fix them. You can always do better. @page @node Macro and Variable Index, General Index, FAQ, Top diff --git a/stamp-vti b/stamp-vti index 250cc3e44..d3020080b 100644 --- a/stamp-vti +++ b/stamp-vti @@ -1,4 +1,4 @@ -@set UPDATED 9 February 2003 +@set UPDATED 23 February 2003 @set UPDATED-MONTH February 2003 @set EDITION 1.7a @set VERSION 1.7a diff --git a/version.texi b/version.texi index 250cc3e44..d3020080b 100644 --- a/version.texi +++ b/version.texi @@ -1,4 +1,4 @@ -@set UPDATED 9 February 2003 +@set UPDATED 23 February 2003 @set UPDATED-MONTH February 2003 @set EDITION 1.7a @set VERSION 1.7a