>Number: 2551
>Category: config
>Synopsis: libexecdir is one of the directory that should be ajusted to
>contain "apache"
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: change-request
>Submitter-Id: apache
>Arrival-Date: Sun Jul 5 23:10:00 PDT 1998
>Last-Modified:
>Originator: [EMAIL PROTECTED]
>Organization:
apache
>Release: 1.3.0
>Environment:
Irrelevent
>Description:
When configuring with --prefix=/usr/local (i.e., a directory which
does not contain "apache" somewhere in its full path), libexecdir is
set by default to /usr/local/libexec while others like datadir are set
to /usr/local/share/apache. It is common practice for packages which
have several files to install in /usr/local/libexec to create their
own subdirectory (emacs and octave, for instance).
There are several reasons why this should also be the case for apache:
. several files are installed
. it's hard for someone to just guess that mod_include.so is an apache
file (in other words, none of the .so file contain apache in their name)
. nothing else than apache needs these files (which is not the case for
libraries which are installed directly in /usr/local/lib)
. apache already does it for etc, include, share, and var (but not
bin, sbin, and man, which is ok: that's common practice too)
(I am aware of the --libexecdir option to configure. I just think
this suggestion would be the best default for those who use /usr/local
instead of /usr/local/apache.)
>How-To-Repeat:
Configure with --prefix=/usr/local.
>Fix:
Here's a patch to configure. Makefile.tmpl may also need to be
changed in the way it ajusts conf/httpd.conf-dist before installation.
--- configure.orig-1.3.0 Fri May 29 16:45:52 1998
+++ configure Mon Jul 6 01:27:55 1998
@@ -727,7 +727,7 @@
val=`echo $val | sed -e 's:/*$::'`
eval "$var=\"$val\""
case $var in
- sysconfdir|datadir|localstatedir|includedir )
+ libexecdir|sysconfdir|datadir|localstatedir|includedir )
eval "val=\$$var"
case $val in
*apache | *apache* ) ;;
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
