Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] BLU's SEO

On 10/18/2013 1:30 PM, John Abreau wrote:
> ... and I put it aside when I realized that my changes would be wiped
> out the next time I ran "yum update".

Not necessarily.  Here's what RPM does if you make local modifications
to a file, and then try to update the package:
 - if the file you modified is identical in both versions of the
package, then the local modifications are kept in-place (zero effort to
maintain your local change)
 - if the file you modified is different in the two packages, RPM
doesn't assume it knows how to munge the two versions with whatever
local modification has been made, so it uses the new version of the file
from the RPM and saves your locally modified version in filename.rpmsave

So yes you have to pay attention to the warnings when you update that "x
was saved as x.rpmsave", but in the case that the file is newer in the
package you probably should be manually re-merging the local change anyway.

Some clever scripting around "yum update" could probably send you a nice
email whenever you need to manually pay attention to something like that...


BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /