On Thu, 2011-03-03 at 10:37 +0100, Tollef Fog Heen wrote: > | Is there any reason against using a debconf script that asks if the > | daemon should be started at boot time (or on which runlevels)? That > | way you can easily modify the configuration with dpkg-reconfigure and > | benefit from the debconf frontends. > > If you use a configuration management framework you probably don't care > that much about debconf, since the debconfiscation of packages is fairly > spotty and doesn't really lend itself to more complex setup. > Imagine having a full nagios or munin configuration done through debconf > and then imagine the preseed needed for that. Compare that with just > dumping a configuration file somewhere. yes, but a proper debconfization should respect/reflect configuration files, so there shouldn't be need for any pre-seeding beyond having the files in place before installing :) > Hooking update-rc.d into debconf is probably not the worst idea in the > world, except update-rc.d is supposed to be run non-interactively and I > think it's the wrong place in the stack to configure that functionaliy. i think it'd have to be a level higher, something kind of like dbconfig-common for initscripts. sean
Attachment:
signature.asc
Description: This is a digitally signed message part