Proposal to add build of kernel-backports package to kernel.spec

John W. Linville linville at redhat.com
Thu Oct 6 16:40:00 UTC 2011


On Thu, Oct 06, 2011 at 12:34:19PM -0400, Dave Jones wrote:
> On Thu, Oct 06, 2011 at 12:21:11PM -0400, John W. Linville wrote:
> 
>  > > Are you proposing this for _just_ 14  ? In which case, I'd be fine with
>  > > that, because we're not rebasing it.
>  > > 
>  > > For 15 onwards, I don't think this is worth it.
>  > 
>  > Until 3.1 is released, F14 is the only release that can use it anyway.
>  > That said, I would like to use it there if nothing else.
>  > 
>  > As for F15 and beyond, current-1 can still be enough delta to cause
>  > problems.  Also, obstacles against updating kernel releases can be
>  > unpredictable.
>  > 
>  > Maybe we could have it in the .spec file for all the releases, but have
>  > it turned-off by default?  Then at least it is there if we need it.
>  > 
>  > Using compat-wireless is a good way to make even more up-to-date
>  > hardware support available in Fedora at nearly no cost to us.  I would
>  > really like to see us take advantage of it.
> 
> Another possibility is just using git-wireless in f15/f16 and beyond.
> Which we've done before..
> 
> I'm thinking along the lines of having stuff just work by default rather
> than having users file bugs when something breaks, and then having to
> tell them 'oh, install compat-wireless'.

You mean just have it in the base kernel package?  I would be happy
with that.  The idea for a seperate package was mostly to give
an escape hatch for those that didn't want the later drivers for
whatever reason.  But if we stick to the compat-wireless releases
based on stable kernels, I don't think there is a great stability
concern with just using them for everyone.

Removing the bits of the patch that generate separate packages
is nearly trivial.  I'll be happy to do that if that is generally
preferred. :-)

John
-- 
John W. Linville		The water won't run clean until you get
linville at redhat.com			the pigs out of the creek.


More information about the kernel mailing list