[pkg-lighttpd] Bug#498951: Bug#498951: closed by Olaf van der Spek <olaf at xwis.net> ()
Olaf van der Spek
olafvdspek at gmail.com
Sun Oct 24 15:01:04 UTC 2010
On Sun, Oct 24, 2010 at 4:54 PM, Jonas Smedegaard <dr at jones.dk> wrote:
> It is non-fatal to invoke lightly-enable-mod when already enabled.
I know, but lighttpd.postinst shouldn't enable any modules if this
isn't a fresh install, right?
> * Encourage package maintainers to first query then enable
Why not an if not enabled flag?
> This would also make it possible for packages to disable conflicting
> modules, which involves checking if exists and enabled, ask for permission
> to disable (as it might be needed by other setup snippets!) and fail the
> package install if not being granted permission.
That sounds too complex.
> Well, that too. But the very thing of listing a bunch of modules commented
> out is a hint to the local admin (and the package maintainer!) that
> uncommenting is the preferred style of configuration here.
ATM there's only rewrite that's commented out. No other modules.
> I do not mean in code, but in the config file.
True, but there should be a warning in the docs.
> * Add low-ordered module snippets for each module provided by lighttpd
Done for most modules already.
> * Add debconf interface to declare space-delimited list of modules to
> enable during install, by default installing only rewrite
Debconf? I don't think that's necessary. And only usable at install time.
More information about the pkg-lighttpd-maintainers