On Sun, Oct 24, 2010 at 03:54:14PM +0200, Olaf van der Spek wrote:
On Sat, Oct 23, 2010 at 11:08 PM, Jonas Smedegaard <[email protected]> wrote:Your package provides an ABI until it breaks. That's normal.What I propose is to use that lightly-enable-mod mechanism for server modules: Provide one file per module, and enable by default the ones you now enable by default in the master file.Hmm, how does one properly create those default symlinks?
Ahem, using lightly-enable-mod.That answer seems so obvious that I suspect perhaps we are talking past each other here, but can't imagine what might be the misunderstanding...
Then other packages can request enabling of modules, and if already enabled, then no harm is done. That is better than other packages providing snippets themselves which both provide configurations and enable modules - because then there is high risk of multiple enabling same module.Have a look at how Apache does similar these days.I've enabled redirect by default in the main conf now, only rewrite is left in there disabled.
Yes. And that's a good start: It is not possible to disable them later. But... * the config file still encourage enabling modules there * there is no warning (that I know of) about multiple enabling modules * you do not provide a mechanism for other packages to enable modules during install.I maintain (more than) 2 packages related to this: cipux-cat-web and sympa.
Today, I would need to have each of those packages provide a snippet which both enable the needed modules and configure patg access etc.
This means installing both packages causes modules to be enabled twice, which you told me is bad.
What I do with those package regarding apache2 is to a) enable needed modules, and b) add a snippet only setting up path access etc.
- Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: Digital signature
