>Number: 2695 >Category: other >Synopsis: Broken directory structure >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Fri Jul 24 07:40:01 PDT 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.1 >Environment: FreeBSD 2.2.5, but I assume its because of the configure script itself. I was using that APACI thing. >Description: My directory exists as /usr/local/etc/apache, I put in ./configure --prefix =/usr/local --sysconfdir=/usr/local/etc/apache
(because httpd exists in /usr/local/sbin so the prefix is /usr/local and my config files are in /usr/local/etc/apache. I also tried /usr/local and /usr/local/etc as the sysconfdirs.) Unfortunately it tacked on /etc/apache again to the end of the sysconfdir. When I use /usr/local it tacks on NOTHING, and when I use /usr/local/etc it tacks on apache/apache.... ... It got so bloody annoying that I finally just made /usr/local/etc/apache/etc/apache and symlinked the conf files. >How-To-Repeat: >Fix: Make sure nothing is appanded to the sysconfdir variable if there is a / after it. Document that feature. Infact, that should be done for all variables =}. I might hack the script later and retarball the dist for archiving (we archive all our current software source). If I do so then Ill be happy to email you the new script for testing. >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. ]
