Re: Need advice on changing kernel.bbclass

["Mike \(mwester\)" <mwester@dls.net>]

----- Original Message ----- 
From: "Marcin Juszkiewicz" <openembedded@hrw.one.pl>
To: <openembedded-devel@lists.openembedded.org>
Sent: Thursday, June 07, 2007 1:39 AM
Subject: Re: [oe] Need advice on changing kernel.bbclass


>
> RPROVIDES_kernel-2.4.22-xfs = "kernel-image-2.4.22-xfs" should solve your
> problem.

I've made the change, and the build is starting...

but I'm not sure about this.  This will instruct ipkg that the package
"kernel-2.4.22-xfs" will satisify the dependency for
"kernel-image-2.4.22-xfs", right?  That's not the problem I've faced with
right now; I don't need to generate extra information for the
kernel-*.ipk --- that won't help the hundreds and hundreds of devices
already installed.  I need instead to alter the information in the generated
kernel-module-*.ipk files so that they do not have a dependency on
kernel-2.4.22-xfs (as the installed devices do not, according to the old
packaging, have that dependency satisfied -- instead they feature only
kernel-image-2.4.22-xfs).
Or do I misunderstand the RPROVIDES/RDEPENDS mechanism?

> Change was in kernel*.bbclass and it was discussed on this list -
> thread "[oe] RFC: Kernel image packaging" from 14 March this year.

I'll dig up that thread for review.  Clearly this is not a high-priority
problem, if it's taken almost 3 months for this issue to surface since this
change to kernel.bbclass was made -- clearly adding kernel modules to the
feeds for the older releases is not a common things any more.  But there is
a (reasonable) request in the queue, so I'd like to find a way to get those
modules built (that doesn't require the user to "upgrade" their installation
entirely, especially since I have no intention at this time of building a
new release for them to upgrade to!)

Thanks!
Mike (mwester)