Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#2960 - Apache config is in /etc/httpd/conf instead of /etc/httpd

Attached to Project: Arch Linux
Opened by Alec Thomas (alecthomas) - Thursday, 14 July 2005, 10:27 GMT
Last edited by Dale Blount (dale) - Friday, 15 July 2005, 18:15 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Very Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Perhaps there is some reason for this, but it escapes me.
This task depends upon

Closed by  arjan timmerman (blaasvis)
Thursday, 22 June 2006, 14:37 GMT
Reason for closing:  Won't fix
Additional comments about closing:  i agree with judd on this, i do the same
Comment by Dale Blount (dale) - Friday, 15 July 2005, 18:15 GMT
all other distro's i've ever seen put configs in /etc/httpd/conf or /opt/etc/httpd/conf if apache is installed in /opt
Comment by Alec Thomas (alecthomas) - Saturday, 16 July 2005, 01:36 GMT
Hello,

I understand what you're saying about Apache having a /conf sub-directory in its installation tree, but I have never seent this before.

Gentoo, Slackware, SuSE place config directly in /etc/apache:

http://mirror.pudas.net/gentoo-x86-portage/net-www/apache/apache-2.0.54-r12.ebuild
http://slackware.it/en/pb/searchfile.php?v=current&c=slackware&string=%2Fetc%2Fapache&w=on
ftp://ftp.suse.com/pub/projects/apache/apache2/9.3-i386/apache2-2.0.54-2.1.i586.rpm

Fedora puts the default config files in /etc/httpd/conf, so presumably does RedHat.

http://download.fedora.redhat.com/pub/fedora/linux/core/4/i386/os/Fedora/RPMS/httpd-2.0.54-10.i386.rpm

(Though they actually have a conf.d and some other config files in /etc/httpd, rather than just a single conf directory)

I guess what I'm trying to say is that it doesn't make much sense to me to have an extra directory inside an otherwise empty directory. It doesn't provide the user with any extra information, given that it is in /etc already and so should be obvious that it is config. I can understand it if it was in /opt/httpd/conf.

I think a simpler layout would be:

/etc/httpd/httpd.conf (and other default config files)
/etc/httpd/conf.d/ (directory for modules, etc.)

So, anyway, that's all I was trying to say :)
Comment by Jan de Groot (JGC) - Saturday, 16 July 2005, 15:30 GMT
The easiest way to solve this "bug" is the way debian did a long while ago:

/etc/apache/conf is a symlink to /etc/apache (yes, that will cause a loop :P)

So we could have /etc/httpd/conf to be a symlink to /etc/httpd and make stuff in the pre_upgrade that moves these files around.
Comment by Judd Vinet (judd) - Saturday, 16 July 2005, 18:19 GMT
Hi Alec,

I understand your point, but I don't really see it as a bug that we need to fix. It's just one of those idiosyncracies that some packages have. I find the conf subdirectory quite handy on servers, actually. For example, on servers with SSL, my /etc/httpd has three directories: conf, keys, and certs.

And adding a conf.d directory is a simple process. I also split my virtual host config into a separate file as well. In Arch style, this is left the to user/admin to set up as s/he pleases.

Loading...