linux-patch packaging best practice.

[Tim Gardner]

On 08/10/2010 08:55 AM, Tim Nowaczyk wrote:
> Hello all,
>
> I created a kernal patch package for our local site,
> linux-patch-web100, that was working fine with hardy.  It seems that
> the "--added-patches" argument to make-kpkg was removed sometime
> between the release of hardy and lucid.  I haven't found any
> discussion of this online.  My question is, what is the current best
> practice for packaging linux kernel patches?  Is it still
> dh-kpatches?  Do I just have to update my README to instruct the
> users to run /usr/src/kernel-patches/all/apply/web100 before
> make-kpkg?  Or, is there a new framework that is now preferred?
>
> Many Thanks, Tim Nowaczyk
>
> -- Timothy Nowaczyk Network Systems Engineer University of Virginia -
> ITC tan7f at virginia.edu
>
>
>
>

Tim - we're all pretty much git centric and do development ala the 
upstream kernel community. As such we (the kernel team) don't apply 
patches to the source package, rather we commit a patch to a local git 
repository and rebuild. There is a boat load of information in the wiki 
beginning at https://wiki.ubuntu.com/Kernel about how we maintain the 
Ubuntu kernel.

rtg
-- 
Tim Gardner tim.gardner at canonical.com