On Thursday 09 June 2005 12:56 pm, observer wrote: > Hi, > First excuse my bad english. > > I've made a rpm that defines both %post and %postun macros and when i > run an upgrade on it both get executed, the postun macro is run after > the post macro an as result of it in therms of the other components of > this app, which is divided in several rpms, this particular component is > not installed because postun makes it look like not installed, which > macros should i choose to make what i have now in post be exectuded > after what i have in postun or none of them be executed when im > upgrading? In %postun, check $1. It will be > 0 for an upgrade, and 0 for a remove in most situations. So, you can conditionally execute stuff in %postun depending on whether it's an upgrade or remove. This means you have to get the old package right... you can't fix it with an upgraded package since the old package's %postun script runs after the new packages scripts. If you have already released a package with a broken %postun, the only way I know of to get around it is with a %triggerpostun http://cpplus.info/DEMO/man/view_docbf1b.html?file=%2Fusr%2Fshare%2Fdoc%2Frpm-4.2.1%2Ftriggers&for=rpm > > Thanks for your help. > > _______________________________________________ > Rpm-list mailing list > Rpm-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/rpm-list -- Bart Whiteley
