Description of problem:
The upgrade process should have a post-reboot process that iterates
through configuration files whose contents need to be merged. Example,
I do a FC2 - FC3 upgrade. I now have an /etc/yum.conf and an
/etc/yum.conf.rpmnew. If I run yum (and it's stock,) it'll try to get
updates for FC2 instead of FC3 (which is wrong.)
The right thing to do is, a GUI package modelled after tkdiff
1. For each rpm package, iterate through known config files.
2. If exists $(dirname)/conf_file.rpm*, put said package name in a
scrollable widget with radio button. You choose of that list of rpm
packages whose config files have changed, which current/rpm* files you
want to diff in a tkdiff-like diffy/merge tool.
3. And you go through and visit each one. The tool of course allows
you to exit after changing one or many or NO conf files (make a
change; check it out)
4. Personally, I like dpkg's concept of "do you want to keep your
changes, overwrite with the packager's conf file, or diff them" that
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This is better solved by fixing RPM's config file algorithm.