Hi, all. Back in the days when I was using Mandriva (which RPM-based), when I updated a package that had a configuration file that I had modified, urpmi was smart enough to realize it, and wouldn't just blindly wipe it out. Instead, it would create a new copy for you to look over and merge. I.E., you'd end up with something like: /etc/somepackage.conf.rpmnew Then after doing the update, I could look for files with .rpmnew at the end and work on making any changes needed. Heck, we even had a really handy script called etc-update which would go through the /etc directory looking for .rpmnew files and would then give you the choice of use the new file, keep the old file (& delete the new one) or merge the two together, which would diff the two and present the changes in groups side-by-side and you'd then select to use the left side (original content) or use the right side (the new content in the .rpmnew file) and you'd go through that until you were done. Regardless of an etc-update like tool, is that how it works in Debian? Does it avoid overwriting config files which have been changed by you since they were installed, and if so, does it put the new content with an easy-to-search-for .something at the end? Thanks! --Dave
Attachment:
signature.asc
Description: OpenPGP digital signature