automake 1.9.5 minor doc updates

[Karl Berry]

In reading through some of the current automake manual, I found a few
small items, see diff below.  The Hello code is in flux, so I didn't
bother to update that.

Two other things I noticed I did not attempt to fix:

1)
    Node: Uniform
       For instance, installation of HTML files is part of Automake, you
    could use this to install raw HTML documentation:
         htmldir = $(prefix)/html
         html_DATA = automake.html

I don't understand this.  Does the user really have to define htmldir?
Isn't that defined by default now?  As written, it seems like the word
"not" is missing, ie, "HTML files is not part of Automake".

2)
    Node: Public macros

I don't perceive any ordering to the macros here.  I suggest putting the
most important ones first, eg, AM_INIT_AUTOMAKE, and the obsolete ones
last -- maybe even in a separate (sub)section.

Cheers,
karl


*** /usr/local/gnu/src/automake-1.9.5/doc/ORIG/automake.texi    Sat Feb 12 
13:16:20 2005
--- /usr/local/gnu/src/automake-1.9.5/doc/automake.texi Sun Mar 27 16:41:09 2005
***************
*** 660,664 ****
  
  Some @code{Makefile} variables are reserved by the GNU Coding Standards
! for the use of the ``user'' -- the person building the package.  For
  instance, @code{CFLAGS} is one such variable.
  
--- 660,664 ----
  
  Some @code{Makefile} variables are reserved by the GNU Coding Standards
! for the use of the ``user''---the person building the package.  For
  instance, @code{CFLAGS} is one such variable.
  
***************
*** 671,675 ****
  any of these variables at build time.
  
! To get around this problem, automake introduces an automake-specific
  shadow variable for each user flag variable.  (Shadow variables are not
  introduced for variables like @code{CC}, where they would make no
--- 671,675 ----
  any of these variables at build time.
  
! To get around this problem, Automake introduces an automake-specific
  shadow variable for each user flag variable.  (Shadow variables are not
  introduced for variables like @code{CC}, where they would make no
***************
*** 708,712 ****
  new architectures and fix probes broken by changes in new kernel
  versions.  You are encouraged to fetch the latest versions of these
! files from @url{ftp://ftp.gnu.org/gnu/config/} before making a release.
  
  @item depcomp
--- 708,714 ----
  new architectures and fix probes broken by changes in new kernel
  versions.  You are encouraged to fetch the latest versions of these
! files from
! @url{http://savannah.gnu.org/cgi-bin/viewcvs/gnulib/gnulib/build-aux/}
! before making a release.
  
  @item depcomp
***************
*** 746,751 ****
  
  @item texinfo.tex
! Not a program, this file is required for @code{make dvi}, @code{make ps}
! and @code{make pdf} to work when Texinfo sources are in the package.
  
  @item ylwrap
--- 748,756 ----
  
  @item texinfo.tex
! Not a program, this file is required for @code{make dvi}, @code{make
! ps} and @code{make pdf} to work when Texinfo sources are in the
! package.  You are encouraged to fetch the latest version from
! @url{http://savannah.gnu.org/cgi-bin/viewcvs/gnulib/gnulib/build-aux/}
! before making a release.
  
  @item ylwrap
***************
*** 840,844 ****
  @cindex GNU Hello, example
  
! @uref{ftp://prep.ai.mit.edu/pub/gnu/hello-1.3.tar.gz, GNU hello} is
  renowned for its classic simplicity and versatility.  This section shows
  how Automake could be used with the GNU Hello package.  The examples
--- 845,849 ----
  @cindex GNU Hello, example
  
! @uref{http://www.gnu.org/software/hello, GNU Hello} is
  renowned for its classic simplicity and versatility.  This section shows
  how Automake could be used with the GNU Hello package.  The examples

Diff finished at Sun Mar 27 16:41:14