Günter Knauf [mailto:[EMAIL PROTECTED]] wrote: > unfortunately we have symlinks only on *nix platforms, so for > all other platforms this isnt a solution... > Guenter.
Unices all? have symlinks and NT supports lins too. Then still people could instead of symlinking the data copy the configs in and out of the enabled dir. On debian they got the two simple commands for that, apachectl could be made to do it to. Greets, Jeroen > > 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.
