From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] using kernel.bbclass rename hook for external modules as well
Date: Sat, 23 Oct 2010 15:14:15 +0200 [thread overview]
Message-ID: <i9un38$trm$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTi=NBNEgPe5j3vb74KTmGJALSmNqbPx_Bg-kKxMu@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 23-10-10 09:46, Frans Meulenbroeks wrote:
> 2010/10/22 Koen Kooi <k.kooi@student.utwente.nl>:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi,
>>
>> Currently kernel.bbclass splits and renames modules into
>> kernel-module-<foo>, but module.bbclass doesn't. What's your opinion on
>> making modules.bbclass follow the same logic for consistency?
>> To make upgrade paths work the 'kernel-modules' metapackage would be
>> ${PN} for external modules.
>
> The idea looks good to be, but can you explain the last sentence?
> I would expect the recipes that use these modules get changed too and
> with a PR bump they will drag in the new module with the new name, and
> not too much additional work needed.
> What I am missing?
Khem asked a similar question which I tried to answer:
http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-October/026053.html
Does that address your question as well?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMwt+nMkyGM64RGpERAhFhAJ9pLDQc9ngI0AB+/t+QAH9SSmnbRgCdHqOZ
O+vzfAYutIkZqD5OOfOBDY8=
=anSR
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-10-23 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 14:56 [RFC] using kernel.bbclass rename hook for external modules as well Koen Kooi
2010-10-22 17:06 ` Chris Larson
2010-10-22 20:44 ` Khem Raj
2010-10-23 8:28 ` Koen Kooi
2010-10-23 7:46 ` Frans Meulenbroeks
2010-10-23 13:14 ` Koen Kooi [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='i9un38$trm$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox