Re: Some more debconf queries
Doh. Forgot to keep the list in the header, which I definitely meant to..
----- Forwarded message from -----
Date: Thu, 11 May 2000 01:05:12 +0100
To: John Goerzen <jgoerzen@progenylinux.com>
Subject: Re: Some more debconf queries
User-Agent: Mutt/1.1.3i
On Wed, May 10, 2000 at 01:33:30PM -0500, John Goerzen wrote:
> OK, last time I was asking about editing conffiles in-place. Let's
> assume that I do. Then, there are some issues:
I'm afraid I didn't read your previous thread, so I hope what I say
doesn't sound contradictory...
The reasons you give below are precisely why you shouldn't alter a
conffile programmatically. If you wish to alter a *configuration
file* programmatically, that's fine, but don't mark it as a conffile.
At least, that's the general rule. Very likely, I missed something in
this specific instance, and hopefully someone will point out what...
>
> * If my debconf scripts edit a conffile, will the user be presented
> with a "replace this conffile" prompt at each upgrade?
> If so, how can we work around this? Will the user know what to do?
>
> * What happens if the user says 'yes' to replace the file? Does
> debconf get rerun so that it can re-edit it with the values
> from the database?
>
> * And what if the user says 'no' but the file really has changed?
> Debconf scripts might expect a different format/file/whatever.
>
> -- John
>
>
> --
> To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
--
Jules Bean | Any sufficiently advanced
jules@{debian.org,jellybean.co.uk} | technology is indistinguishable
jmlb2@hermes.cam.ac.uk | from a perl script
----- End forwarded message -----
--
Jules Bean | Any sufficiently advanced
jules@{debian.org,jellybean.co.uk} | technology is indistinguishable
jmlb2@hermes.cam.ac.uk | from a perl script
Reply to: