Best practices for patch management on RPM based packages?

Panu Matilainen pmatilai at
Tue Sep 6 14:29:23 UTC 2011

On 09/06/2011 05:16 PM, Richard Shaw wrote:
> Most of the packages I work with have very few patches so it's not all
> that difficult, but there are a couple of packages I'm working with
> that have a lot of patches and one of them has a very active upstream
> (which is a good thing!) but that also means that the patches need
> frequent adjustment.
> I like the idea of quilt but I can't seem to find the magic recipe to
> get it to integrate with rpmbuild.

There's a long-standing RFE to integrate quilt/git/etc into rpmbuild to 
ease the patch management, I just never seem to get around to it. There 
are things that can make it easier already though, for example:

Also if you're just tired and bored with having to refer to each patch 
twice just to get it applied, the %{patches} macro can help there too as 
long as all the patches can be applied with the same flags, you can do 
something like this:

for p in %{patches}; do
     patch -p1 < ${p} || exit 1

	- Panu -

More information about the devel mailing list