On Sun, Oct 24, 2010 at 05:01:04PM +0200, Olaf van der Spek wrote:
On Sun, Oct 24, 2010 at 4:54 PM, Jonas Smedegaard <d...@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?
Ah, we were talking about different things, then.Other packages, e.g. sympa, should be allowed to simply enable at each install or upgrade.
lighttpd should respect active system setup, if any. That's right.
* Encourage package maintainers to first query then enableWhy not an if not enabled flag?
You tell me: Why not? ;-)NB! Beware that negated questions is hostile: you effectively accuse your opponent of being against your proposal by default. I am not.
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.
Too complex for what? for being possible, of priority to you, relevant to other package maintainers, or something else?
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.
What are you talking about?A freshly installed lighttpd_1.4.28-1_amd64.deb in Debian Sid contains this at the top of /etc/lighttpd/lighttpd.conf:
server.modules = (
"mod_access",
"mod_alias",
"mod_compress",
# "mod_rewrite",
# "mod_redirect",
# "mod_usertrack",
# "mod_flv_streaming",
# "mod_evasive"
)
I do not mean in code, but in the config file.True, but there should be a warning in the docs.
Sure, there too.
* Add low-ordered module snippets for each module provided by lighttpdDone for most modules already.
Ah, yes. Great!
* Add debconf interface to declare space-delimited list of modules to enable during install, by default installing only rewriteDebconf? I don't think that's necessary. And only usable at install time.
None of this is "necessary". Debconf would be beneficial both for Debian Pure Blends and others wanting to to preseed a custom setup and for later sysadmin editing using dpkg-reconfigure.
If you don't want your packaging to be nice in this area, then don't. - 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
