Make documentation and error messages of APACI's --activate-module=FILE

option more clear.

Submitted by: Jan Wolter <janc@wwnet.net>
PR: 3995


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@82888 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 9 insertions, 8 deletions

diff --git a/INSTALL b/INSTALL
index 6205da414f..8438decfb1 100644
--- a/INSTALL
+++ b/INSTALL
@@ -238,14 +238,15 @@
      to automatically include a simple third-party module to the Apache build
      process.
  
-     Use the --activate-module=FILE option to on-the-fly add an entry for an
-     existing module source file in the configuration file. FILE has to be a
-     valid path under src/modules/ of the Apache source tree, i.e. it already
-     has to be copied to this location before.  The module is automatically
-     enabled. Use this option to automatically include a complex third-party
-     module to the Apache build process where, for instance a module like
-     mod_perl or mod_php3 consisting of more than one file which are created by
-     a third-party configuration scheme.
+     Use the --activate-module=FILE option to add an entry for an existing
+     module source file into the configuration file on-the-fly. FILE has to be
+     a valid path beginning with "src/modules/", and the file has to have been
+     copied to this location in the Apache source tree before running
+     configure.  The module is automatically enabled. Use this option to
+     automatically include a complex third-party module to the Apache build
+     process where, for instance a module like mod_perl or mod_php3 consisting
+     of more than one file which are created by a third-party configuration
+     scheme.
  
      Use the --enable-module=NAME and --disable-module=NAME options to enable
      or disable a particular already distributed module from the Apache