Re: .rpmsave vs .rpmnew

[Jeff Johnson <jbj JBJ ORG>]

On Wed, Jul 25, 2001 at 12:31:30PM -0400, Alan Eldridge wrote:
> >> >> So I have a config file I have changed. I install the new rpm. My config
> >> >> file gets renamed to .rpmsave. My configuration is no longer in place. This
> >> >> contradicts the behavior you described.
> >> >>
> >> >> The file is marked (noreplace).
> >> >
> >> >its only marked noreplace in the rpm you've just installed, not the one
> >> >that is already in the db.
> >> >
> >> 
> >> File is marked noreplace in both rpms. (Extreme case: they're the same rpm.)
> >> Still, existing file is moved to .rpmsave.
> >> 
> >
> >*Why* do you want a file to be installed with extension .rpmnew?
> >
> >You can always just put the extension on the file in package.
> 
> I don't want the existing conf renamed. The existing conf should still work

Hmmm, the existing config is renamed to .rpmsave and/or .rpmorig, that's a
whole different algorithm/disposition involving FA_SAVE/FA_BACKUP than the
FA_ALTNAME .rpmnew extension disposition for the file from the new package.

> after installation without manual intervention to rename a file back.  I
> want "noreplace" to really mean exactly that.
> 

Well, noreplace means exactly what it's always meant, and that's more
complicated than
	Always install as foo.rpmnew.
even though the intuitive meaning of "noreplace" would seem to indicate
otherwise. There's absolutely no reason to change, IMHO, what's already
implemented is complicated enough, and any change is going to be encumbered
with critically important lagacy incompatibilities. Not gonna happen ...

What that means to you is that there are conditions under which an incoming
file is *not* installed with a .rpmnew extension even if marked
%config(noreplace), so you need to deal with that.

73 de Jeff

-- 
Jeff Johnson	ARS N3NPQ
jbj@jbj.org	(jbj@redhat.com)
Chapel Hill, NC