[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: rebuilding anaconda-9.0-4 src
- From: "Alexander Rau" <alex rau ca>
- To: "Taylor, ForrestX" <forrestx taylor intel com>
- Cc: <anaconda-devel-list redhat com>
- Subject: Re: rebuilding anaconda-9.0-4 src
- Date: Wed, 1 Oct 2003 15:21:42 -0400
Since I like the idea of my changes being portable I want to try my luck
using your patch method.
I followed your instructions and everything went fine until
rpmbuild -ba anaconda.spec
I get the following error:
error: No patch number 1
Which folder shoud I be in? According to your description I am in cd
/usr/src/redhat/SPECS
Thanks
AR
----- Original Message -----
From: "Taylor, ForrestX" <forrestx taylor intel com>
To: "Alexander Rau" <alex rau ca>
Cc: <anaconda-devel-list redhat com>
Sent: Wednesday, October 01, 2003 2:02 PM
Subject: Re: rebuilding anaconda-9.0-4 src
> Alexander Rau wrote:
> > Thanks a bunch Forrest:
> >
> > I admit, when it comes to tinkering with src packages I am a newbie.
> >
> > Could you explain what you mean by the portability of the patch method?
>
> Sure. I mean that it is easier to send out a patch to others than it is
> to send out the src.rpm file. It is also easier when the next version
> of anaconda comes out to port your patches over to the new release (if
> it hasn't been fixed in the newer version). I started out using the tar
> method, and I found that it was much easier to use patches. I would
> often have to make changes to newer version, and I had forgotten exactly
> what I had done in the source. Now, I can just look at the patches, and
> copy them over to the newer version.
>
> Forrest
> --
>
>
>
> _______________________________________________
> Anaconda-devel-list mailing list
> Anaconda-devel-list redhat com
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]