On Fri, 03 Apr 2009 16:15:40 -0700, Scott Silva wrote:
> on 4-3-2009 2:40 PM Joseph L. Casale spake the following:
>>> Folks, be sure to do an updatedb and then locate rpmsave and rpmnew
>>> after upgrading the system. Then you can make sure your local changes
>>> get propagated into the updated system.
>>
>> If the case is a file gets overwritten, and not a case of a file gets
>> copied to a new one called *.rpm{save|new} during an upgrade, what
>> exactly does the above do?
> That is what them backup thingies are for!
i agree with your backup argument.
actually, backup thingies can prove worthful in other scenarios too.
but restores are only necessary when something or somehow messed
something up. in the perfect world backups are taken but a restore is
never necessary.
anyhow, i am not sure what could be done better. if a rpm builder forgets
to define a file correct than it will be overwritten, of course. i am
sitting in front of a OS-X right now. if apple does an update, files are
overwritten *poof* . but rpm provides the infrastructre to do it right.
thats a good thing, but its not foolproof of course.
so, backup. please.
best regards,
markus