This is a philosophical question as well as a technical question... I've build an RPM for 'my' version of 'bash'. But (for other technical reasons) someone in the future will eventually issue an 'rpm -e bash' during our upgrade procedure, which will attempt to remove the bash binary file. But... a) a lot of other packages are dependant on bash, and b) without at least some version of bash, the system will probably come crashing to a halt. :-( What is the recommended technique to: a) allow 'rpm -e bash' and avoid the dependency complaint/failure? b) prevent the binary from being removed during package removal? or how can you maintain a copy of the binary across package removal. And can all this be done within the spec file? TIA Fulko This document is strictly confidential and intended only for use by the addressee unless otherwise stated. If you are not the intended recipient, please notify the sender immediately and delete it from your system. _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
