apache1 configdir

[Elan Ruusamäe]

On Wednesday 29 December 2004 23:16, Adam Gołębiowski wrote:
> If there are triggers, I see no reasons not to switch to configdir. And
> it's still not too late to have it done in Ac.
okay, i've completed spec so far that on clean system it reads configs from 
conf.d

there are few issues,
the config dir should be /etc/apache/conf.d (current one uses conf.d)
or more like apache2 has, /etc/apache/httpd.conf?

i prefer the NAME.d variant(compare /etc/env.d, /etc/xinetd.d, /etc/profile.d)

in case of upgrade the original apache.conf remains to system, should the 
trigger modify /etc/apache/apache.conf after upgrade by adding the new 
features to it (include /etc/apache/conf.d) or should the .rpmnew being 
placed instead of the old one (mv apache.conf apache.conf.old && mv 
apache.conf.rpmnew apache.conf)

also as the new one does not use apxs to place loadmodule directives to 
config, but these rather came from rpm. the issue is difficult for core 
modules, should the AddModule and ClearModuleList directives being wiped out 
with sed? or if the .rpmnew move (in previous section) is being used this is 
not neccesary.

also perhaps each module directives should be split out from big apache.conf 
to configdir? (it goes very out of control if the .rpmnew is not used)

here's the current diff
http://glen.alkohol.ee/pld/apache1-confdir.3.diff

and srpm
http://glen.alkohol.ee/pld/apache1-1.3.33-1.30.src.rpm

if only my opinion matters, then i'd do trigger that puts .rpmnew into active 
and old apache.conf is stored as apache.conf.rpmold and split each module 
config to configdir

action 

-- 
glen