rpmbuild question - follow on to gcc issues

[Michael Schwendt]

On Tue, 10 Feb 2009 14:00:23 -0500, Steve wrote:

> ---- "Mikkel L. Ellertson" wrote: 
> > One way is to create your own patch that is used after the original
> > patch. Add it to the end of the patch list.
> 
> Yukk!! That will get really tiresome really quickly. At this point I don't really know what I'm looking for so I may end up having to add debug statements to several files.
> 

Yes, that's in the nature of incremental patches. You would usually try to
get patches merged upstream regularly. And if upstream doesn't do that for a
long time, you may need to rediff patches occasionally. Or join them with
a private working-copy of the source code tree in order to reduce the number
of patches to apply in a src.rpm. With a high number of patches and many
modifications in the same files, maintaining a private patched source code tree
may be the more convenient solution.

> Is there a way to apply all the patches to the source code and them remove them from the spec file?
> 

"rpmbuild -bp foo.spec" and then tar the build dir. That's not what's done
in Fedora, though.