All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] hello-mod: Ensure the produced package name begins with kernel-module-
Date: Fri, 12 Apr 2013 22:41:56 +0200	[thread overview]
Message-ID: <20130412204156.GX2477@jama> (raw)
In-Reply-To: <CADkTA4Nxoa2=q8++zuJyoa-eHCYa+Q1bf-r1Eu8z4h4Li7xzOw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2786 bytes --]

On Fri, Apr 12, 2013 at 04:06:56PM -0400, Bruce Ashfield wrote:
> On Fri, Apr 12, 2013 at 3:42 PM, Mark Hatle <mark.hatle@windriver.com> wrote:
> > The special key kernel-module- is necessary for the system to avoid a package
> > rename when installing a multilib image.  For example:
> >
> > local.conf: IMAGE_INSTALL_append = " hello-mod"
> >
> > bitbake lib32-core-image-minimal
> >
> > The system will translate names and prepend 'lib32-', unless the package
> > begins with kernel-module-.
> 
> Mark and I were talking about this, and since this is something that is required
> in a multlib system, and an external module has gone to the trouble of
> inheriting
> module.bbclass, and we have the kernel-module-split.bbclass, that this
> is something
> we should be able to programatically do and generate the package names that
> meet the expectations of the system.
> 
> I suggested a bugzilla and we can tackle this at the front end of the upcoming
> dev cycle.
> 
> I think that's reasonable, if anyone knows of a reason why this absolutely can't
> be done automatically .. or I'm out to lunch, I'm happy to have my
> redirect, NAK'd :)

Agreed, hello-mod should give good example and 
inherit kernel-module-split

if it does not work as-is now then we should improve kernel-module-split and
hello-mod.

> >  meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> >
> > diff --git a/meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb b/meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb
> > index 64a6dda..621f700 100644
> > --- a/meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb
> > +++ b/meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb
> > @@ -13,3 +13,11 @@ SRC_URI = "file://Makefile \
> >            "
> >
> >  S = "${WORKDIR}"
> > +
> > +# Kernel module packages MUST begin with 'kernel-module-', otherwise
> > +# multilib image generation can fail.
> > +#
> > +# The following line is only necessary if the recipe name does not begin
> > +# with kernel-module-.
> > +#
> > +PKG_${PN} = "kernel-module-${PN}"
> > --
> > 1.8.1.2.545.g2f19ada
> >
> >
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> 
> 
> 
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      parent reply	other threads:[~2013-04-12 20:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 19:42 [PATCH] hello-mod: Ensure the produced package name begins with kernel-module- Mark Hatle
2013-04-12 20:06 ` Bruce Ashfield
2013-04-12 20:11   ` Mark Hatle
2013-04-12 20:41   ` Martin Jansa [this message]

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=20130412204156.GX2477@jama \
    --to=martin.jansa@gmail.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@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.