Re: Informations for packaging apache(2) third party modules
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 off developing your own solution to the problem though. Of course, so I compared a lot of other apache modules and mix what I think the best wayi, because they all use a different approach (auto enabling, doing nothink, asking, ...) I'm not a DD, just a new maintainer so I can't help directly to put officials docs online, but I ask someone who want to work with me on an official apache module packaging webpage. Once a standard skeleton for postinst/prerm scripts, we can talk to each already packaged modules maintainers for adopting this universal way. :) -- Emmanuel LACOUR - [EMAIL PROTECTED]
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 - [EMAIL PROTECTED]
Re: Informations for packaging apache(2) third party modules
* 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 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). 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 off developing your own solution to the problem though. Cheers, -Thom -- That sounds like a lot of work... Can we out source? The Revolution will not be outsourced! (Slick/Monique - Sinfest)
Informations for packaging apache(2) third party modules
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 a2enmod without asking the user... AW, is there a place where I can find informations on packaging tools with dependendies on apache like apache modules. If there isn't such a place I would suggest to set up a simple page or wiki (I can do this) and add a link to Packaging section on Developers' Corner at www.debian.org. Regards, -- Emmanuel LACOUR - [EMAIL PROTECTED]
Re: Informations for packaging apache(2) third party modules
* 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 some other packages and saw that often they simply a2enmod without asking the user... AW, is there a place where I can find informations on packaging tools with dependendies on apache like apache modules. If there isn't such a place I would suggest to set up a simple page or wiki (I can do this) and add a link to Packaging section on Developers' Corner at www.debian.org. libapache2-mod-macro is pretty much the simplest possible case for an apache2 module. get the source for that, and run with it. -Thom -- That sounds like a lot of work... Can we out source? The Revolution will not be outsourced! (Slick/Monique - Sinfest)
