Andreas Putzo wrote: >> 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.
Sorry, I forgot to mention that I just exactly uploaded the fixed package around the time I wrote my message. > Which i'm not fully agree with because you break > for example unattended updates that use debconf frontend > 'noninteractive' and --force-confold presumably. Not sure what --force-confold does, but it sounds like "Shooting yourself in the foot in 5 minutes" to me. And if people really prefer such a setting, they'll probably be fine with such a comment missing. > Maybe it's better to not use /etc/default/bitlbee at all? Problem is, how do I still make the port# configurable? One thing I could do is grep bitlbee.conf for ^DaemonPort= and if it exists (so without a #) don't supply the -p flag. Getting a bit hackish now.. but it may be nice to do. > Isn't ucf capable to handle bitlbee.conf? > Not sure what ucf does, and I'd really prefer to spend the little amount of time I have on upstream development of BitlBee, not on its packaging. :-) If you're fluent with ucf and could show me something nifty, I'm open for patches! Cheers, Wilmer v/d Gaast. -- +-------- .''`. - -- ---+ + - -- --- ---- ----- ------+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---------------+ +------ ----- ---- --- -- - +
signature.asc
Description: OpenPGP digital signature
