All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC][PATCH] module bbclass: split each module into a kernel-module-<foo> subpackage and use PN as metapackage
Date: Sat, 23 Oct 2010 20:15:19 +0200	[thread overview]
Message-ID: <i9v8nn$303$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTinLeN9pCrmwtZYxv7HhLgzfhq+HKhkBm0hLpm9x@mail.gmail.com>

-----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@gmail.com> wrote:
> 
>> From: Koen Kooi <k-kooi@ti.com>
>>
>> Signed-off-by: Koen Kooi <k-kooi@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 :)

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMwyY2MkyGM64RGpERAvl7AJ9vvDrrfJoJv2uWbBYFNMtmUSQBlQCgqyU/
g7/rxYKqcNnGn5ar1d+mFSY=
=9tBi
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-10-23 18:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-23 13:45 [RFC][PATCH] module bbclass: split each module into a kernel-module-<foo> subpackage and use PN as metapackage Koen Kooi
2010-10-23 17:03 ` Chris Larson
2010-10-23 18:15   ` Koen Kooi [this message]
2010-10-23 19:15     ` Chris Larson
2010-11-02 12:38   ` Koen Kooi
2010-10-25 23:00 ` Khem Raj
2010-10-25 23:13   ` Chris Larson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='i9v8nn$303$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.