Re: How to handle erasing an RPM that contains a mandatory file

[bob proulx com (Bob Proulx)]

Fulko Hew sita aero wrote:
> I've build an RPM for 'my' version of 'bash'.

I recommend starting from a known good packaging of bash and then
simply making your modifications to it.  Then you won't have to be
doing these types of hacks that you are now trying to do.

> But (for other technical reasons) someone in the future will
> eventually issue an 'rpm -e bash' during our upgrade procedure,

I think needing to do that is incorrect.  I would fix it so that they
will not be needing to erase bash "for other technical reasons".  It
will be a source of problems.

> What is the recommended technique to:
> 
> a) allow 'rpm -e bash' and avoid the dependency complaint/failure?

Don't do it.

> b) prevent the binary from being removed during package removal?
>    or how can you maintain a copy of the binary across package removal.

Don't do it.  Simple is better than complicated schemes to work around
problems caused by doing bad things.

Why do you want to erase bash but leave it on the system?

Bob