Look at how your distro does it.  Debian has a utility called ucf for managing the 3way diff between old default, new default, and currently installed.  It does require some setup though and isn't necessarily obvious.  There are other tools and other distros for this.

You can also look at using something like git or svn.  Read up on how to track a "vendor branch" using your tool of choice.

On Mon, Mar 22, 2010 at 11:59 AM, Michael Collins <msc@freeswitch.org> wrote:


On Sat, Mar 20, 2010 at 10:54 PM, Yehavi Bourvine <yehavi.bourvine@gmail.com> wrote:
Hello,
 
  Once a week I upgrade our production system by retreiving freeswitch-1.0.5-latest.tar.gz, building and installing it. This updates all the binaries, but I am left with the current config files (which is good, as some of them contains locally edited data). The problem is how to detect (and merge) changes in the configuration files, like new parameters. I can do manual diffs, but it is a time consuming task.
 
What is the BCP of doing such an upgrade?

I would do automated diffs from a script. In fact, it might be easiest to diff the new default configs against the existing default configs so that you only see what was changed in the past week. That would be less noisy than diffing against your modified config files.

How's your bash scripting skills? :)
-MC


_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org




--
-Rupa