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

[John W. Linville]

On Wed, Nov 16, 2011 at 04:19:16PM -0500, Dave Jones wrote:
> On Thu, Oct 06, 2011 at 12:50:44PM -0400, Dave Jones wrote:
>  > On Thu, Oct 06, 2011 at 12:40:00PM -0400, John W. Linville wrote:
>  >  
>  >  > > 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.
>  > 
>  > yeah.
> 
> So what happened here? We seemed to have agreement that compat-wireless
> didn't make sense, and that we'd just carry git-wireless, but I see you
> just committed compat-wireless to f16/master.
> 
> confused.

Hmmm...I guess there was some misunderstanding between us.  I reckon
that I didn't catch that you were making a distinction between
compat-wireless and my tree that it pulls from.  I thought the
objection was to building a separate package from the kernel spec.

FWIW, using the compat-wireless version is a lot less work, since all
the backporting bits should be done already.  And it takes advantage
of the backporting skills of the members of that project, rather
than relying solely on me.  I think it is a better way to proceed,
and one I can actually commit to doing.

> (also, having it be a tarball is a pain wrt review)

True, but I'm not sure that a giant patch w/ all the wireless-next
bits in it would be any easier on the eyes...?

What I have there now is only a build option.  I wanted a little
time to make sure it is building correctly and whatnot before I sent
everyone down that path.  I was planning to turn it on for rawhide
before too long, and undecided about when I might do that with F16.

Do you have any suggestions?  I don't really see compat-wireless as
any big danger, and certainly not any bigger danger than a patch
from wireless-next.

I would still be open to building a separate backports package instead,
if I misunderstood that objection.  That is what the brown distro
does, FWIW.

So, how to proceed?

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