> It's a matter of a 3-way merge, as cvs does it. The three files are: > 1) Old package version original config file > 2) New package version config file > 3) The installed config file (with your changes). > > This would mean changing dpkg to keep pristine copies of installed > conffiles (file 1 above) so the comparison and merge could be done.
Hrm. OK, I see what you mean indeed. I never really thought about how CVS works. Keeping pristine copies might not be much of a hack. If you choose not to use the new version, it goes in as a .dpkg-dist file anyway. So all it would take is forcing that to always happen, and keeping track to replace the old one with the new one after the merge. > This is something I would love, but never have the time to do anything > about. I'm not sure whether the politics or the code seem more daunting. This really is an excellent idea though. Any idea where I should begin? It's pointless to code it if Debian balks at the idea. It would take seventeen million kinds of testing too. I would guess bringing about significant changes to something as fundamental as dpkg is no easy thing. -- Michael McIntyre ---- Silvan <[EMAIL PROTECTED]> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
