Config modified?
Charles R. Anderson
cra at WPI.EDU
Tue Oct 12 23:21:20 UTC 2004
On Tue, Oct 12, 2004 at 04:57:42PM -0600, Rodolfo J. Paiz wrote:
> Since when? RPM's default behavior for *years* has been to upgrade the
> package and then either create an rpmnew config file so you can migrate
> in your changes, or save your old config in an rpmsave file for the same
> purpose. I've never seen it flat-out *refuse* to upgrade something
> before.
RPM didn't change. up2date did.
> Think of it from a beginner user's point of view (which I'm not, but
> Fedora is not "experts-only" so we should try to be friendly to them).
> If up2date refuses to even get me the new package, how am I supposed to
> get beyond this? Go fire up my trusty command-line FTP client, go to
> mirror, find the file, download it, use cpio to extract the config file,
> diff it, *then* update the package?
It is just the default setting. The settings dialog is brought up the
first time the user clicks on the pulsing red icon in the notification
area.
> I liked the old behavior one hell of a lot better. I don't see this
> being very user-friendly at all, but rather more of an obstacle to most
> users getting their packages updated.
I don't like it either, but at least it can be changed.
More information about the fedora-test-list
mailing list