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

[John W. Linville]

On Thu, Oct 06, 2011 at 03:55:41PM -0400, Andy Gospodarek wrote:
> On Thu, Oct 06, 2011 at 09:35:19PM +0200, Thorsten Leemhuis wrote:
> [...]
> > > diff --git a/depmod-dist.conf b/depmod-dist.conf
> > > index 8513288..0585676 100644
> > > --- a/depmod-dist.conf
> > > +++ b/depmod-dist.conf
> > > @@ -3,4 +3,4 @@
> > >  #
> > >  
> > >  # override default search ordering for kmod packaging
> > > -search updates extra built-in weak-updates
> > > +search updates extra backports built-in weak-updates
> > 
> > And what exactly would be the difference between "updates" and
> > "backports"? Might be wise to at least mention it with a sentence or two
> > in the docs if there is actually one. Is there is: Is it relevant for
> > users or just creating confusion?
> > 
> 
> The term 'backports' was chosen specifically not to interfere with drivers
> that may come from out-of-tree drivers and and get installed in
> 'updates.'  The point was to avoid confusion as people might wonder why
> the out-of-tree driver they download and install broke something that
> was installed from a Fedora package.
> 
> Based on Dave and John's continued conversation this might not be
> necessary as the default may be to use the drivers from the compat tree
> rather than having them as an extra package.

Well, they still need to be installed somewhere.  Putting them
somewhere other than their own directory (whatever the name) would
require more hacking into the compat-wireless package than I intended
to do.

The reason for naming putting it somewhere other than updates (packaged
external modules) or extras (locally-built external modules) was
to indicate that these modules were something other than the other
categories.  That still seems reasonable to me.

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