www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Wolter <j...@wwnet.net>
Subject documentation/3995: Ambiguity in INSTALL's description of --activate-module flag
Date Thu, 04 Mar 1999 15:55:41 GMT

>Number:         3995
>Category:       documentation
>Synopsis:       Ambiguity in INSTALL's description of --activate-module flag
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          doc-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Mar  4 08:00:01 PST 1999
>Last-Modified:
>Originator:     janc@wwnet.net
>Organization:
apache
>Release:        1.3.4
>Environment:
-
>Description:
The INSTALL file says:

     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.

to me, "a valid path under src/modules/" means something like "extra/mod_foo.c".
I had to read the configure script to understand that what was meant was a path
beginning with src/modules/, like "src/modules/extra/mod_foo.c".

Suggested wording:

     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 begining with "src/modules/", and the file has to have been
     copied to this location in the Apache source tree before running configure.

Getting even more trivial, the grammar of the error message:

  Error: Module source already has to stay below src/modules/ to be activated

makes me cringe.  How about:

  Error: Module source already has to be below src/modules/ to be activated

Anyway, thanks for a great product.
>How-To-Repeat:
-
>Fix:
-
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]




Mime
View raw message