Cfg-update has such a logic. It looks for user changes, If there are decisions to make at all and previous decisions.
Ihatethespellcheckerofmyphone. Am 31.05.2011 08:49 schrieb "Alan McKinnon" <alan.mckin...@gmail.com>: On Tue, May 31, 2011 at 12:08 AM, David W Noon <dwn...@ntlworld.com> wrote: > On Mon, 30 May 2011 21... The logic appears to be that an unmodified file will be re-instated as-is should the package be re-merged, so nothing changes. A modified config file is more problematic - if the package is re-merged, which version should be used? The old one or the new vanilla one? Presumably the user modified the file last time round for a reason and that reason might still be valid. Only one sensible choice remains - present both files to the human user and ask them to decide. If memory serves, this is in some doc somewhere, I know I read it long ago but don't remember where. -- Alan McKinnon alan dot mckinnon at gmail dot com
