Extent INSTALL.gen by information on external installation.

1 files changed, 73 insertions, 30 deletions

diff --git a/INSTALL.gen b/INSTALL.gen
index 095b1eb4..8acefaab 100644
--- a/INSTALL.gen
+++ b/INSTALL.gen
@@ -1,12 +1,78 @@
 Installation Instructions
 *************************
 
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 Free
-Software Foundation, Inc.
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2006
+Free Software Foundation, Inc.
 
 This file is free documentation; the Free Software Foundation gives
 unlimited permission to copy, distribute and modify it.
 
+Normal Installation
+===================
+
+The simplest way to compile this package is:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./configure' to configure the package for your system.  If you're
+     using `csh' on an old version of System V, you might need to type
+     `sh ./configure' instead to prevent `csh' from trying to execute
+     `configure' itself.
+
+     Running `configure' takes awhile.  While running, it prints some
+     messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package.
+
+  4. Type `sudo make install' to install the programs and any data
+     files and documentation.  `make install' is the only step for
+     which you need `root' access; this is done by `sudo'.
+
+  5. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+External Installation
+=====================
+
+It is also possible to perform the whole installation process outside
+of the source code.  In this case a whole external build directory
+structure is created without changing any parts of the source code.
+This is usefule when the source code is read-only or when several
+different installations, such as for multiple architectures should be
+constructed.
+
+As an example, let's assume that the source code of the `groff' code
+is in `/usr/local/src/groff' and that the installation should be done
+with the directory `/home/my/groff.compile'.
+
+  0. Run `cd /home/my/groff.compile'.
+
+  1. Call `/usr/local/src/groff/configure' in that directory to
+     configure the package for your system.  If you're using `csh' on an
+     old version of System V, you might need to type
+     `sh /usr/local/src/groff/configure' instead.
+
+  2. Type `make' to compile the package in that directory.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package.
+
+  4. Type `sudo make install' to install the programs and any data
+     files and documentation.
+
+  5. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.
+
 Basic Installation
 ==================
 
@@ -39,34 +105,6 @@ may remove or edit it.
 `configure.ac' if you want to change it or regenerate `configure' using
 a newer version of `autoconf'.
 
-The simplest way to compile this package is:
-
-  1. `cd' to the directory containing the package's source code and type
-     `./configure' to configure the package for your system.  If you're
-     using `csh' on an old version of System V, you might need to type
-     `sh ./configure' instead to prevent `csh' from trying to execute
-     `configure' itself.
-
-     Running `configure' takes awhile.  While running, it prints some
-     messages telling which features it is checking for.
-
-  2. Type `make' to compile the package.
-
-  3. Optionally, type `make check' to run any self-tests that come with
-     the package.
-
-  4. Type `make install' to install the programs and any data files and
-     documentation.
-
-  5. You can remove the program binaries and object files from the
-     source code directory by typing `make clean'.  To also remove the
-     files that `configure' created (so you can compile the package for
-     a different kind of computer), type `make distclean'.  There is
-     also a `make maintainer-clean' target, but that is intended mainly
-     for the package's developers.  If you use it, you may have to get
-     all sorts of other programs in order to regenerate files that came
-     with the distribution.
-
 Compilers and Options
 =====================
 
@@ -229,3 +267,8 @@ overridden in the site shell script).
 `configure' also accepts some other, not widely useful, options.  Run
 `configure --help' for more details.
 
+Emacs settings
+==============
+Local Variables:
+mode: text
+End: