gnustandards ChangeLog standards.texi

[Karl Berry]

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       08/07/27 16:55:06

Modified files:
        .              : ChangeLog standards.texi 

Log message:
        configure specification, no implementation mandated

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/ChangeLog?cvsroot=gnustandards&r1=1.75&r2=1.76
http://cvs.savannah.gnu.org/viewcvs/gnustandards/standards.texi?cvsroot=gnustandards&r1=1.180&r2=1.181

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -b -r1.75 -r1.76
--- ChangeLog   9 Jul 2008 13:19:31 -0000       1.75
+++ ChangeLog   27 Jul 2008 16:55:05 -0000      1.76
@@ -1,3 +1,9 @@
+2008-07-27  Karl Berry  <address@hidden>
+
+       * standards.texi (Configuration): make clear that this is the
+       specification and that autoconf/automake are not the required
+       implementation.
+
 2008-07-09  Karl Berry  <address@hidden>
 
        * maintain.texi (Clean Ups): correct section title (Tips and

Index: standards.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/standards.texi,v
retrieving revision 1.180
retrieving revision 1.181
diff -u -b -r1.180 -r1.181
--- standards.texi      10 Jun 2008 18:54:48 -0000      1.180
+++ standards.texi      27 Jul 2008 16:55:06 -0000      1.181
@@ -3,7 +3,7 @@
 @setfilename standards.info
 @settitle GNU Coding Standards
 @c This date is automagically updated when you save this file:
address@hidden lastupdate June 10, 2008
address@hidden lastupdate July 25, 2008
 @c %**end of header
 
 @dircategory GNU organization
@@ -3774,15 +3774,23 @@
 Each GNU distribution should come with a shell script named
 @code{configure}.  This script is given arguments which describe the
 kind of machine and system you want to compile the program for.
-
 The @code{configure} script must record the configuration options so
 that they affect compilation.
 
-One way to do this is to make a link from a standard name such as
address@hidden to the proper configuration file for the chosen system.
-If you use this technique, the distribution should @emph{not} contain a
-file named @file{config.h}.  This is so that people won't be able to
-build the program without configuring it first.
+The description here is the specification of the interface for the
address@hidden script in GNU packages.  Many packages implement it
+using GNU Autoconf (@pxref{Top,, Introduction, autoconf, Autoconf})
+and/or GNU Automake (@pxref{Top,, Introduction, automake, Automake}),
+but you do not have to use these tools.  You can implement it any way
+you like; for instance, by making @code{configure} be a wrapper around
+a completely different configuration system.
+
+Another way for the @code{configure} script to operate is to make a
+link from a standard name such as @file{config.h} to the proper
+configuration file for the chosen system.  If you use this technique,
+the distribution should @emph{not} contain a file named
address@hidden  This is so that people won't be able to build the
+program without configuring it first.
 
 Another thing that @code{configure} can do is to edit the Makefile.  If
 you do this, the distribution should @emph{not} contain a file named