G�nter Knauf [mailto:[EMAIL PROTECTED]] wrote: > > Ahhh, but you forget that not everyone uses DSO modules. > Many people > > compile the modules into the server, and for them the > module is active > > regardless of the LoadModule line. > Ok, that was the point I missed and convinces me that it's > not such a good idea then... > > then let's make another suggestion: > let's create a modules.conf and move these configs into it, > and perhaps also the mod_deflate config; then this conf can > easily be included from the httpd.conf, and httpd.conf > becomes simpler...
Better do the configs the 'debian way' then: /etc/apache2/ containing: apache2.conf : default config for running Apache2 minimally. ports.conf : "Port 443" etc directives httpd.conf : local site extra's modules-available/ : containing a config file per module modules-enabled/ : containing symlinks to the modules-available directory Now if you want a module enabled; you can symlink it, easy and obvious configging for everybody ;) The apache2.conf "includes" the ports.conf + httpd.conf + modules-available ofcourse. As for packagers, let your apache module depend on the main apache package and install your module's config into the available dir, then _ask_ the user if they want it enabled at once. Greets, Jeroen
