Hi, On Jun 07 21:27, Debian Bug Tracking System wrote: > #530804: /etc/default/bitlbee overwrites values in bitlbee.conf > > It has been closed by Wilmer van der Gaast <wil...@gaast.net>. > > I consider this bug "fixed". I added a clear comment to bitlbee.conf > saying that the Debian init script overrides this value with what's in > /etc/default/bitlbee.
Notice the version of the package i was referring to which does not have your comments. It's usually better to close a bug with a version if it is already fixed. Which i'm not fully agree with because you break for example unattended updates that use debconf frontend 'noninteractive' and --force-confold presumably. But i'm not going to reopen the bug. After all, it's your decision how you want to handle the configuration :) > I agree that it'd be nicer to not have this hack at all, but for that > I'd have to do some fragile in-place bitlbee.conf editing in the > maintainer script which I'm not too excited about. :-/ > > I'm open to suggestions on how this could be done easily and reliably. I'm usually a fan of /etc/default/* but in this case i found it annoying because it broke my setup. I don't know how other packages deal with it but in my opinion it would be a better solution if the values from bitlbee.conf are used in favour of debconf if they are not commented. Though i understand that this would be hard to implement, since usually command line options override config files. Maybe it's better to not use /etc/default/bitlbee at all? Or you could try to provide reasonable defaults, e.g. what's currently used in bitlbee.conf. Isn't ucf capable to handle bitlbee.conf? Thank's for packaging bitlbee btw :) Cheers, Andreas
signature.asc
Description: Digital signature
