IIRC this was briefly mentioned in the past, but I'd like to hear from the Apache team if there is still interest/consideration in providing a programmatic module enable/disable interface (CLI).
In Debian there is a2enmod and a2dismod which are used to enable/disable available Apache modules. As we start to include more and more optional modules which drop their optional but disabled-oob config into samples-conf.d, it might be nice to provide a tool for users to selectively enable some of them by name. The workaround is of course to simply 'cp samples-conf.d/foo.conf conf.d/' so it is not a vital tool, but would be nice to have a stable interface/CLI for scripting instead of requiring everyone to bake in the absolute path to the samples and conf dirs into their scripts. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
