[oe] [RFC][PATCH] module bbclass: split each module into a kernel-module-<foo> subpackage and use PN as metapackage

Chris Larson clarson at kergoth.com
Sat Oct 23 19:15:11 UTC 2010


On Sat, Oct 23, 2010 at 11:15 AM, Koen Kooi <k.kooi at student.utwente.nl>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 23-10-10 19:03, Chris Larson wrote:
> > On Sat, Oct 23, 2010 at 6:45 AM, Koen Kooi <koen.kooi at gmail.com> wrote:
> >
> >> From: Koen Kooi <k-kooi at ti.com>
> >>
> >> Signed-off-by: Koen Kooi <k-kooi at ti.com>
> >>
> >> ---
> >>  classes/module.bbclass |  191
> >> ++++++++++++++++++++++++++++++++++++++++++++++-
> >>  1 files changed, 186 insertions(+), 5 deletions(-)
> >>
> >
> >
> > How about moving the common functions into oe.module or oe.package and
> using
> > them from module.bbclass and kernel.bbclass?
>
> I thought about that, but that needs more work :( We need to pass in a
> different path to System.map, use PN as metapackage name, use a
> different blacklist, etc.
> That requires a lot more python skill than I currently have.
>
> Apart from the horrendous code duplication, how does this look? It seems
> to do the right thing for the recipes I tested with :)
>

Looks reasonable otherwise, can always consolidate in a second pass later
on.

Acked-by: Chris Larson <chris_larson at mentor.com>
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics



More information about the Openembedded-devel mailing list