RPM Community Forums

Mailing List Message of <rpm-users>

Creating patch rpms

From: Derek Pressnall <derekpr2@needcaffeine.net>
Date: Sat 07 Nov 2009 - 20:01:28 CET
Message-ID: <1209f0450911071101r58241f4dp2a8f28bdef9b4389@mail.gmail.com>
I've got a packaging issue I'm trying to resolve.
Our application consists of a several hundred files (mostly input
forms and sql files).  Periodically the developers release patch sets
to add specific features or resolve issues, which consists of about a
about a dozen or so files.  These files are either in addition to, or
replacement of, files that are part of the original application.

Now normally with RPM, you would release a new package version and use
that to update the previous version.  The problem is that customers
each get a unique set of these patches (one customer may get patches
1, 17, and 25, while another will get patch 8, 17, and 31).  Now what
I'd like to do is install the main package rpm, then roll out an rpm
for each patch set (and use RPM's dependency tracking to force
dependent patches to be installed).  But the problem comes in that
many of the files included in the patch sets conflict with existing
files in the parent RPM, which would require the --force flag to be
used.  Furthermore, it would show the parent package as having corrupt
files (since the new files are owned by the patches).

Is there any to package a set of files and tell RPM that it "enhances"
another package, so it would a) let you install it despite conflicts
(without --force), and b) keep the parent package & children packages
grouped together (so that when the parent package is upgraded, any
patches included with the new version get removed from the RPM
database)?

Thanks.
Received on Sat Nov 7 20:40:33 2009
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.