From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2] module.bbclass: fix dependency on specific kernel
Date: Thu, 14 Oct 2010 01:06:22 +0200 [thread overview]
Message-ID: <4CB63B6E.4010305@opendreambox.org> (raw)
In-Reply-To: <AANLkTim2hP8QOog74zab1gtBr3o=cXPEx4mLoKn6C8Oq@mail.gmail.com>
On 10/14/2010 12:30 AM, Chris Larson wrote:
> On Wed, Oct 13, 2010 at 3:09 PM, Andreas Oberritter <obi@opendreambox.org>wrote:
>
>> * Previously, the kernel version did not show up in the
>> generated control file (debian ipk).
>> * Use the same format as in kernel.bbclass.
>>
>> Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
>> ---
>> classes/module.bbclass | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/classes/module.bbclass b/classes/module.bbclass
>> index 0e0018e..601a882 100644
>> --- a/classes/module.bbclass
>> +++ b/classes/module.bbclass
>> @@ -1,4 +1,4 @@
>> -RDEPENDS_${PN} += "kernel (${KERNEL_VERSION}) update-modules"
>> +RDEPENDS_${PN} += "kernel-${KERNEL_VERSION} update-modules"
>> DEPENDS += "virtual/kernel"
>>
>
> This looks just plain wrong to me. kernel-<version> is bitbake build time
> syntax, kernel (<version>) is runtime syntax for dpkg/opkg.
Does this mean that kernel.bbclass is wrong, too? Because kernel.bbclass
calls do_split_packages with extra_depends='update-modules
kernel-${KERNEL_VERSION}', which translates to
RDEPENDS_kernel-module-foo = "update-modules kernel-${KERNEL_VERSION}".
Regards,
Andreas
prev parent reply other threads:[~2010-10-13 23:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 22:09 Patches from opendreambox.org #2 Andreas Oberritter
2010-10-13 22:09 ` [PATCH v2] module.bbclass: fix dependency on specific kernel Andreas Oberritter
2010-10-13 22:30 ` Chris Larson
2010-10-13 23:06 ` Andreas Oberritter [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=4CB63B6E.4010305@opendreambox.org \
--to=obi@opendreambox.org \
--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.