On Wed, Oct 3, 2012 at 04:16:22 +0200, Hector Romojaro wrote: > Only the changes between the lines "## Debconf changes (DO NOT EDIT > BYHAND) ##" and "## End Debconf Changes ###################" are > overwritten. > > The idea behind this was: > - If the file wasn't modified by the user, then the upgrade is performed > smoothly and the new config.local file is generated with the old debconf > values. > - If the "debconf block" was modified by hand by the user, then > overwrite the changes with the debconf ones in config.local. It should > be ok, because there was a warning about not doing that. > - If another block of the file was modified by the user, then prompt him > about the changes, as with any other config file. > > Now, i realise that i'm assuming that the user should only use debconf > to modify these changes (database settings, via package reconfigure), > should i give the user the chance to edit this settings by hand, > checking them on preinst and replacing the current debconf values with > the modified ones? > That would seem better, yes. The existing configuration file should be the authoritative source for the existing configuration. debconf is not a registry, and all that. Cheers, Julien
Attachment:
signature.asc
Description: Digital signature