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

2004-10-11 Thread Emmanuel Lacour
On Wed, Sep 15, 2004 at 07:25:11PM +0100, Thom May wrote: u-a-m is a work in process, which will be the standard way of handling modules. It's pretty close, but not there yet. I'm hoping to have some time the next couple of days to work on it and test it etc. I'd really ask you *not* to go

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

2004-09-15 Thread Emmanuel Lacour
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

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

2004-09-15 Thread Thom May
* Emmanuel Lacour ([EMAIL PROTECTED]) wrote : 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

Informations for packaging apache(2) third party modules

2004-09-14 Thread Emmanuel Lacour
Hi everybody, I'm working on packaging a new apache module for apache/apache2 (www.suphp.org), and I try to find the best way for my postinsts/prerms scripts. I found the README.modules in apache-dev, but nothing for apache2-dev. So I looked at some other packages and saw that often they simply

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

2004-09-14 Thread Thom May
* Emmanuel Lacour ([EMAIL PROTECTED]) wrote : Hi everybody, I'm working on packaging a new apache module for apache/apache2 (www.suphp.org), and I try to find the best way for my postinsts/prerms scripts. I found the README.modules in apache-dev, but nothing for apache2-dev. So I looked at