Best practices for patch management on RPM based packages?

Jesse Keating jkeating at j2solutions.net
Wed Sep 7 04:32:23 UTC 2011


On Sep 6, 2011, at 6:52 PM, Mathieu Bridon wrote:
> On Tue, 2011-09-06 at 15:04 -0500, Richard Shaw wrote:
>>> On 09/06/2011 09:53 PM, Matej Cepl wrote:
>>>> What's wrong with
>>>> 
>>>> quilt setup specname.spec
>> 
>> Because rpmbuild segregates everything, quilt doesn't seem to know how
>> to handle that.
>> 
>> When you create the directory tree for rpmbuild it (at some point) creates:
>> 
>> BUILD
>> BUILDROOT
>> RPMS
>> SOURCES
>> SPECS
>> SRPMS
>> 
>> Of course the only ones of intrest to quilt is SOURCES and SPECS but
>> that means they are not in the same directory.
> 
> I have this in my ~/.rpmmacros:
> %_topdir    %(pwd)
> %_sourcedir %(pwd)
> %_specdir   %(pwd)
> %_srcrpmdir %(pwd)
> 
> This way, I simply do:
> $ fedpkg clone foobar
> $ cd foobar
> 
> And I can rpmbuild directly in the git tree.
> 
> Hope that helps.


Don't forget that there is also 'fedpkg local', as well as prep, compile, install.  Some of these have --short-circuit options as well to speed up testing.

- jlk




More information about the devel mailing list