RFC on packaging of additional Apache2 modules
Fri Nov 25 08:35:00 GMT 2005
On Fri, November 25, 2005 6:08 am, Igor Pechtchanski wrote:
> On Thu, 24 Nov 2005, Max Bowsher wrote:
>> I'm preparing a new Apache 2 release, and want to include a conf.d
>> arrangement to allow additional module packagess to install
>> configuration fragments in a useful way.
>> So far, my tentative proposal is:
>> Include /etc/apache2/conf.d/*.conf in httpd.conf.
>> Have module packages install config fragments to
>> /etc/apache2/conf-std.d/, and copy them insto conf.d if no equivalent
>> This is consistent with the way the package currently handles
>> httpd.conf, etc.
>> I'm posting here for input before I go ahead and do it.
> The above sounds fine, but why not use /etc/defaults/etc/apache2/conf.d/
> instead of /etc/apache2/conf-std.d/?
That's amost the same as Debian is doing (the only linux I'm running atm)...
/ some standard apache config stuff then lines to include...
# Include module configuration:
# Include all the user configurations:
# Include ports listing
# Include generic snippets of statements
/ site specific config files (I think)
/ any standard vars (I've not got any)
/ this file is basically empty too
/ usual magic instructions
/ contains *all* known module information
/ contains links to the modules in mods-available you want to use
/ just a listen 80 instruction here!
/ Huh, think you can guess ;)
/ contains all sites you might want this installation of apache to host
/ links to the sites to you want to enable from sites-available
/ ssl files
Hope this helps.
PS, I agree with Igor, untar the installation files into
/etc/defaults/etc/apache2/... and postinstall copy as appropriate :)
More information about the Cygwin-apps