Re: Vi backspace key problem

["Chester R. Hosey" <Chester Hosey gianteagle com>]

On Wed, 2005-07-20 at 02:34 +0200, Dag Wieers wrote:
> 
> That's why it is important to replace as few config-files as possible. If 
> a config-file (like /etc/bashrc) has not been touched, an upgrade will 
> replace the file with the new default.
> 
> Whatever you have put in /etc/bashrc yourself could have gone into 
> /etc/profile.d/
> 
> In some cases this is not possible, but it is always better to first look 
> at your options and weigh them, before changing a config-file. Otherwise 
> you have to clean up the .rpmsave and .rpmnew files yourself.
> 
> PS I've once written a tool in bash to help in cleaning up leftover files 
> like .rpmnew, .rpmsave and .rpmorig and I desperately need to rewrite that 
> in python (allowing to diff available files, verifying with rpmdb and 
> being smart about it in general :))
> 
> Kind regards,
> --   dag wieers,  dag wieers com,  http://dag.wieers.com/   --
> [all I want is a warm bed and a kind word and unlimited power]

>From the wishlist-entries-I-don't-care-enough-to-code-myself dept:

When run interactively and faced with modified configuration files, dpkg
prompts the user and allows them to choose whether to keep the original,
install the upstream version, run a shell to examine the situation, or
examine a diff between the versions.

It's a nice feature. It would be nice if up2date-with-rpm did something
similar, or if RHN noted that an upgrade didn't include a configuration
file update due to user changes. I'd be really impressed if RHN went to
far as to provide a diff of the configuration files so the administrator
could evaluate the importance without having to log in and search
for .rpm{new|save|orig} files manually.

Chet