Re: Informations for packaging apache(2) third party modules
- To: debian-apache@lists.debian.org
- Subject: Re: Informations for packaging apache(2) third party modules
- From: Emmanuel Lacour <elacour@home-dn.net>
- Date: Mon, 11 Oct 2004 23:15:45 +0200
- Message-id: <[🔎] 20041011211545.GA4004@home-dn.net>
- In-reply-to: <20040915182511.GC13198@fandango.home.clearairturbulence.org>
- References: <20040914223220.GA22557@home-dn.net> <20040915015228.GB21083@fandango.home.clearairturbulence.org> <20040915152809.GA29283@home-dn.net> <20040915182511.GC13198@fandango.home.clearairturbulence.org>
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 - elacour@home-dn.net
Reply to: