Building kernel RPMs with patches from git

[Jim Gettys]

I have to second/third Dave's description of how to best do development:
upstream as much as possible is the only sane long term plan. Carrying
patches costs you again, and again, and again, and again....  The sooner
all OLPC specific kernel stuff is fully upstream in Linus' tree, the
happier I'll (and I'm sure Andres) will be.

                         - Jim


On Thu, 2008-05-08 at 11:46 +0100, David Woodhouse wrote:
> On Thu, 2008-05-08 at 10:06 +1200, Martin Langhoff wrote:
> > Dennis, David,
> > 
> > There is right now something that I am having trouble understanding
> > how it's done - related to kernel packaging. Is there any
> > documentation on how the RH team manages kernels with additional
> > patches?
> > 
> > All I can find is tips to manage the patches as patches, but that is
> > so oldstyle. I want a git-integrated workflow... or quilt or whatever.
> > What I would like to do is to track the appropriate git branch that RH
> > has for F7 kernels, and merge in the Libertas patches. Right now we
> > are doing a pretty hackish thing ;-)
> > 
> > Is there anything like this? I'm sure the RH kernel team is using _some_ dscm...
> 
> Actually, we don't. It really is just patches -- and we try to have as
> few of those as possible.
> 
> We don't normally do development directly on the packaged kernel. The
> real development happens in rawhide, which tracks upstream -- so we work
> on the upstream kernel's git tree. Then we can just create patches and
> add them to the RPM.
> 
> I believe there is a way to make quilt use RPM specfiles. I've never
> really bothered looking it up, though -- others may know more, if you
> ask in the right places (like fedora-kernel-list, which I've added to
> Cc).

-- 
Jim Gettys <jg at laptop.org>
One Laptop Per Child