|
If you can write a shell script to do this validation and/or the
removal, then you can either embed it in the spec file or call a script
remotely from inside the spec file. I posted a page the shows how to
embed some shell commands and where they really are in the structure of
the rpm. Say putting it in the %install section is my suggestion. Hope
it helps as I did with adding the cron entries which was a simple copy
(cp). I have seen some spec examples that actually call shell programs.
My personal opinion is you should copy the external shell script to the
working directory (the tar-gz file with the spec file as in the
example) and run it from there, and then let the rpm program delete it. http://www.logiqwest.com/TechnicalPapers/rpmScriptInstall.html This is an example I have from a spec file: %install sh ./installer.sh Barry R Cisna wrote: Hello List, I've looked high and low and all the .spec file examples do not show how to do this IF it is at all possible. How could I do an .spec file entry , possibly %pre --- something to parse the rpm database and if a particular rpm is found to be installed it will be uninstalled during the rpm install process? This is so my rpmbuild/ rpm -ivh does not conflict with a few already exsiting /bin files. I am rolling a few binaries into my rpm that would conflict with already installed .rpm. I'm just trying to make this as streamlined as possible. Thanks, Barry _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxxxxx http://lists.rpm.org/mailman/listinfo/rpm-list --
| |||||||||||||||||||
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxxxxx http://lists.rpm.org/mailman/listinfo/rpm-list
