[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Informations for packaging apache(2) third party modules

On Wed, Sep 15, 2004 at 02:52:28AM +0100, Thom May wrote:
> libapache2-mod-macro is pretty much the simplest possible case for an
> apache2 module.
> get the source for that, and run with it.

I'm not looking for the easiest package example, I already looked at
many, but I wan't to find the best way for postinst/prerm scripts. I
think it's a good idea to provide a choice for the user to
enable/disable the module via debconf at install time and via
dpkg-reconfigure. If there isn't a standard way like with apache1.x, I
will do my debconf template myself (enable/disable modue? yes/no, then
use a2enmod or a2dismod).

There is also a script called "update-apache2-modules". Should I use
this one instead of a2*mod. Is there a standard way for looking if a
module is enabled (other than -e /etc/apache2/mods-enabled/....load).

All I wanted to say in my email is that we should have a standard way
for handling modules with apache2 and we have to document it ... and I'm
ok to help doing this of course:)

Emmanuel LACOUR - elacour@home-dn.net

Reply to: