On Mon, Jan 15, 2001 at 07:40:00PM +1000, Jason Henry Parker wrote: > Joey Hess <joeyh@debian.org> writes: > > > It has recently come to my attention that several developers are using > > debconf as an excuse to write a quick hack rather than doing things > > right. In particular I am talking about several packages that use > > debconf to prompt the user for information, then write the information > > to a file in /etc, and when upgraded or reconfigured, clobber any > > manual changes to the file (and no, I'm not just talking about > > lilo). > > libnss-ldap is a perfect example. I reported this behaviour[1] in > version 123-2 (see Bug#78805). The maintainer's response has been to > upload a version of the package that has reset the question's seen > flag to false. This, of course, does nothing whatsoever to preserve > local settings of other values, or changes to debconf-prompted > questions. > > In general, I don't think debconf has any business interfering with a > `once-only' file like lilo.conf and libnss-ldap.conf, or a > system-critical file like libnss-ldap.conf[2] after the initial > installation of the package and answering of questions. > > jason > > [1] : Actually the file in question was a conffile as well as being > edited by debconf, but whatever. > > [2] : Mistakes in this file make the system unusuable until a reboot > to single-user mode. > -- > ``Banks *are* bastards.'' -- John Laws > > > -- > To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org I'm making a new version that will ask you a question for all the values you can have into /etc/libnss-ldap.conf. Regards, -- Davide Puricelli, evo@windnet.it | apurice@tin.it Debian Developer: evo@debian.org | http://www.debian.org PGP key: finger evo@debian.org UIN: 2885982
Attachment:
pgpyKZDbZ8NaA.pgp
Description: PGP signature