From 5337983bcb95b90198e06c767ec1fbcc487003d0 Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Tue, 25 Mar 2008 06:52:49 -0700 Subject: [PATCH] autoupdate --- doc/maintain.texi | 4 ++-- doc/make-stds.texi | 23 ++++++++++++++++------- 2 files changed, 18 insertions(+), 9 deletions(-) diff --git a/doc/maintain.texi b/doc/maintain.texi index cd4e581fda..fc7a006a51 100644 --- a/doc/maintain.texi +++ b/doc/maintain.texi @@ -5,7 +5,7 @@ @c For double-sided printing, uncomment: @c @setchapternewpage odd @c This date is automagically updated when you save this file: -@set lastupdate March 14, 2008 +@set lastupdate March 21, 2008 @c %**end of header @dircategory GNU organization @@ -549,7 +549,7 @@ To update the list of year numbers, add each year in which you have made nontrivial changes to the package. (Here we assume you're using a publicly accessible revision control server, so that every revision installed is also immediately and automatically published.) When you -add the new year, it is not required to keep track which files have +add the new year, it is not required to keep track of which files have seen significant changes in the new year and which have not. It is recommended and simpler to add the new year to all files in the package, and be done with it for the rest of the year. diff --git a/doc/make-stds.texi b/doc/make-stds.texi index 58edda4aca..041a08515e 100644 --- a/doc/make-stds.texi +++ b/doc/make-stds.texi @@ -33,7 +33,10 @@ chapter @end iftex describes conventions for writing the Makefiles for GNU programs. Using Automake will help you write a Makefile that follows these -conventions. +conventions. For more information on portable Makefiles, see +@sc{posix} and @ref{Portable Make, Portable Make Programming,, autoconf, +Autoconf}. + @menu * Makefile Basics:: General conventions for Makefiles. @@ -144,8 +147,10 @@ subtargets) work correctly with a parallel @code{make}. @section Utilities in Makefiles Write the Makefile commands (and any shell scripts, such as -@code{configure}) to run in @code{sh}, not in @code{csh}. Don't use any -special features of @code{ksh} or @code{bash}. +@code{configure}) to run under @code{sh} (both the traditional Bourne +shell and the @sc{posix} shell), not @code{csh}. Don't use any +special features of @code{ksh} or @code{bash}, or @sc{posix} features +not widely supported in traditional Bourne @code{sh}. The @code{configure} script and the Makefile rules for building and installation should not use any utilities directly except these: @@ -162,12 +167,16 @@ ln ls mkdir mv pwd rm rmdir sed sleep sort tar test touch true Compression programs such as @code{gzip} can be used in the @code{dist} rule. -Stick to the generally supported options for these programs. For -example, don't use @samp{mkdir -p}, convenient as it may be, because -most systems don't support it. +Generally, stick to the widely-supported (usually +@sc{posix}-specified) options and features of these programs. For +example, don't use @samp{mkdir -p}, convenient as it may be, because a +few systems don't support it at all and with others, it is not safe +for parallel execution. For a list of known incompatibilities, see +@ref{Portable Shell, Portable Shell Programming,, autoconf, Autoconf}. + It is a good idea to avoid creating symbolic links in makefiles, since a -few systems don't support them. +few file systems don't support them. The Makefile rules for building and installation can also use compilers and related programs, but should do so via @code{make} variables so that the -- 2.30.2