rpmbuild question - follow on to gcc issues

[Mikkel L. Ellertson]

Steve wrote:
> ---- "Mikkel L. Ellertson" <mikkel at infinity-ltd.com> 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.
> 
> Is there a way to apply all the patches to the source code and
> them remove them from the spec file?
> 
> Steve
> 
Well, if you are debugging the program, you would probably be better
off running "rpmbuild -bp <package>" and then make your changes in
the build directory. Then run make manually. You can do this all as
a normal user. Depending on what you are building, you may be able
to run it as a normal user from the build directory. If not, you are
probably going to override the make file so it installs relative to
your home directory. Once you have it debugged, you can transfere
the changes to the virgin source with a patch, or pass them upstream...

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20090210/d126f91e/attachment-0001.sig>