Creating RPM with Conflicting Files

[Jen Tille]

The problem is the first RPM was released years ago and is on many systems.  I can't change it now.  I only have control over the second RPM.

I have to include pydoc in the second RPM because some systems may not have the first RPM, only the second.

I can install the second RPM with a --replacefiles but if possible, I'd rather not make the users add that special command.  



________________________________
 From: Stuart D. Gathman <stuart at bmsi.com>
To: Jen Tille <jen.tille at yahoo.com>; General discussion about the RPM package manager <rpm-list at lists.rpm.org> 
Sent: Wednesday, March 7, 2012 9:52 AM
Subject: Re: Creating RPM with Conflicting Files
 
Long ago, Nostradamus foresaw that on Mar 6, Jen Tille would write:

> I bundle python along with several other packages into my own RPM and
> release to my clients. 
> My old RPM and new RPM contain the same file: /usr/local/bin/pydoc  so my
> new RPM conflicts and won't install.
> 
> Some systems may have both RPMs installed while others may only have the new
> RPM. 
> How can I create the new RPM so it will overwrite the pydoc file if the
> system has the old RPM?

Put the pydoc (and any other common files) into its own RPM, and make both
RPMs depend on it.

--
          Stuart D. Gathman <stuart at bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-list/attachments/20120307/efa75ba0/attachment.html>