Re: Problems with using debconf in init script...
On Mon, Jan 29, 2001 at 05:26:54PM -0800, Philippe Troin wrote:
> Anthony Towns <email@example.com> writes:
> > On Mon, Jan 29, 2001 at 05:02:56PM -0800, Philippe Troin wrote:
> > > Anthony Towns <firstname.lastname@example.org> writes:
> > > > Use, umm, /etc/default/<service> then. See bug #66912, which should be
> > > > in policy version 220.127.116.11.
> > > This does not apply to the case where the /etc/default/<service> file
> > > might be changed by debconf...
> > Why not? Just create /etc/default/<service> in the postinst instead of
> > making it a conffile...
> What happens if someone makes some changes to /etc/default<service> and than
> dpkg-reconfigure <service> is ran ? Overwrite manual changes ?
This has come up before, and the usual answer is that the maintainer is
responsible for ensuring that the user's manual changes are not overwritten.
Unfortunately, there is no standard way to do this, so everyone does it
differently. Some get it more right than others, but IMO, no package currently
does this to the same level as the conffile mechanism, which is what is