From: Andreas Oberritter <obi@opendreambox.org>
To: Darren Hart <dvhart@linux.intel.com>
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 17:55:22 +0200 [thread overview]
Message-ID: <4F957B6A.7050108@opendreambox.org> (raw)
In-Reply-To: <4F9575B9.7030601@linux.intel.com>
On 23.04.2012 17:31, Darren Hart wrote:
>
> On 04/17/2012 06:05 AM, Andreas Oberritter wrote:
>> * depmod already gets executed by pkg_postinst_kernel-image.
>
> What if you install a module package after the initial system
> installation? Don't you want the module install to run depmod?
If you look at the patch, you see that only the calls to cross-depmod
get removed (which get called during do_rootfs). The behaviour of
modules installed after the initial installation hasn't changed. What
has changed in addition is that modules.bbclass' pkg_postinst doesn't
return an error during do_rootfs, but instead behaves like
pkg_postinst_modules from kernel.bbclass.
Regards,
Andreas
>
> --
> 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
>> 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
>> }
>>
>> EXPORT_FUNCTIONS do_compile do_install
>
next prev parent reply other threads:[~2012-04-23 16:05 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 [this message]
2012-04-23 17:35 ` Darren Hart
2012-04-23 21:21 ` Andreas Oberritter
2012-04-23 21:26 ` Darren Hart
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=4F957B6A.7050108@opendreambox.org \
--to=obi@opendreambox.org \
--cc=dvhart@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox