search for: pwaterma

On 28/06/15 02:17, Joseph L. Casale wrote: > Your script within the rpm should have the logic. Clearly if > you know how to update it, you know how to identify if it > needs updating. Thanks Joseph. I am aware of this option, but it would be only a last resort, because checking the format of the config file is error-prone. I would prefer RPM to tell me the old and new version numbers,

...ands. Well normal convention would be if you replace then the old one gets appended with .rpmsave, if you are not replacing then the new one gets appended with .rpmnew. On the other hand, check this out: https://www.redhat.com/promo/summit/2010/presentations/summit/opensource-for-it-leaders/thurs/pwaterma-2-rpm/RPM-ifying-System-Configurations.pdf Seems you are in luck, you can infer what exists by virtue of the order upgrades are installed. Hth, jlc

I'm trying to get my head around RPM trigger scripts - but currently getting very confused ... I have a custom RPM which has in its spec file a '%triggerin' script for the 'kernel' RPM - i.e. a script that I want to run when the kernel RPM is upgraded/installed This works OK - once my custom RPM is installed, if the kernel is subsequently upgraded/installed, my trigger