From: Darren Hart <dvhart@linux.intel.com>
To: Andreas Oberritter <obi@opendreambox.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/5] {kernel, module}.bbclass: don't run depmod for module packages during do_rootfs
Date: Mon, 23 Apr 2012 14:26:35 -0700 [thread overview]
Message-ID: <4F95C90B.8030007@linux.intel.com> (raw)
In-Reply-To: <4F95C7F1.7030500@opendreambox.org>
On 04/23/2012 02:21 PM, Andreas Oberritter wrote:
> On 23.04.2012 19:35, Darren Hart wrote:
>>
>>
>> On 04/17/2012 06:05 AM, Andreas Oberritter wrote:
>>> * depmod already gets executed by pkg_postinst_kernel-image.
>>>
>>
>> Please include a description of the errors seen that this fixes. This
>> makes it easier for people experiencing this to find the fix.
>
> Well, there is no error. If you build a module using module.bbclass,
> pkg_postinst returns 1 in do_rootfs, causing pkg_postinst to run again
> on first boot. To improve this situation, I copied pkg_postinst from
> kernel.bbclass to module.bbclass. This was rejected by Koen, because he
> doesn't like the code from kernel.bblcass, which uses
> ${STAGING_DIR_KERNEL}. Richard then suggested that calling depmod during
> do_rootfs wasn't necessary at all, because it already gets done by
> kernel-image. I already explained this in the cover letter and in the
> previous email thread.
Apologies if I missed some context. However, the detail needs to be in
the commit log, not the cover letter, as the commit log is where
developers will look for the rationale and justification of a change.
--
Darren
>
>>
>>> Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
>>> ---
>>> meta/classes/kernel.bbclass | 4 +---
>>> meta/classes/module.bbclass | 7 +++----
>>> 2 files changed, 4 insertions(+), 7 deletions(-)
>>>
>>> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
>>> index 3519e7c..c21ab96 100644
>>> --- a/meta/classes/kernel.bbclass
>>> +++ b/meta/classes/kernel.bbclass
>>> @@ -276,9 +276,7 @@ fi
>>> }
>>>
>>> pkg_postinst_modules () {
>>> -if [ -n "$D" ]; then
>>> - ${HOST_PREFIX}depmod -A -b $D -F ${STAGING_KERNEL_DIR}/System.map-${KERNEL_VERSION} ${KERNEL_VERSION}
>>> -else
>>> +if [ -z "$D" ]; then
>>
>> I understand it parallels the previous test - but it seems fragile to
>> rely on the mere existence of $D. Consider the following?
>>
>> if [ ! -d "$D" ]; then
>>
>> This will do the right thing if D is empty as well as if $D is defined
>> by bitbake.
>>
>>> depmod -a
>>> update-modules || true
>>> fi
>>> diff --git a/meta/classes/module.bbclass b/meta/classes/module.bbclass
>>> index 53c16b7..91628e4 100644
>>> --- a/meta/classes/module.bbclass
>>> +++ b/meta/classes/module.bbclass
>>> @@ -37,15 +37,14 @@ module_do_install() {
>>> }
>>>
>>> pkg_postinst_append () {
>>> - if [ -n "$D" ]; then
>>> - exit 1
>>> - fi
>>> +if [ -z "$D" ]; then
>>> depmod -a
>>> update-modules || true
>>> +fi
>>> }
>>>
>>> pkg_postrm_append () {
>>> - update-modules || true
>>> +update-modules || true
>>
>> Unintentional whitespace change?
>>
>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-04-23 21:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 13:05 [PATCH 0/5] Misc resent patches for master or master-next Andreas Oberritter
2012-04-17 13:05 ` [PATCH 1/5] {kernel, module}.bbclass: don't run depmod for module packages during do_rootfs Andreas Oberritter
2012-04-23 15:31 ` Darren Hart
2012-04-23 15:55 ` Andreas Oberritter
2012-04-23 17:35 ` Darren Hart
2012-04-23 21:21 ` Andreas Oberritter
2012-04-23 21:26 ` Darren Hart [this message]
2012-04-17 13:05 ` [PATCH 2/5] mirrors: remove snapshot.debian.net Andreas Oberritter
2012-04-17 13:05 ` [PATCH 3/5] python: use PKGSUFFIX for libpython2 Andreas Oberritter
2012-04-17 13:05 ` [PATCH 4/5] wpa-supplicant: remove unused files Andreas Oberritter
2012-04-17 13:05 ` [PATCH 5/5] wpa-supplicant: move wpa_passphrase to bindir Andreas Oberritter
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=4F95C90B.8030007@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=obi@opendreambox.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox