public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 5/6] kernel.bbclass: remove references to update-modules
Date: Wed, 23 Jan 2013 10:22:51 +0200	[thread overview]
Message-ID: <50FF9DDB.7040807@intel.com> (raw)
In-Reply-To: <50FEFB12.5060905@linux.intel.com>



On 01/22/2013 10:48 PM, Darren Hart wrote:
>> -    use_update_modules = oe.utils.contains('DISTRO_FEATURES', 'update-modules', True, False, d)
>> > -    if use_update_modules:
>> > -        postinst = d.getVar('pkg_postinst_modules', True)
>> > -        postrm = d.getVar('pkg_postrm_modules', True)
>> > -    else:
>> > -        postinst = None
>> > -        postrm = None
>> > +    postinst = d.getVar('pkg_postinst_modules', True)
>> > +    postrm = d.getVar('pkg_postrm_modules', True)
> This seems to be inverted logic from the original. If update-modules is
> removed, then use_update_modules should be false right? Which would have
> previously set postinst and postrm to None.
I believe both the previous and current logic are right:
  * Before, the update-modules script was called in the postinst/postrm.
So, when the update-modules package was not part of the build, the
postinst/postrm could not call update-modules anymore. As a consequence,
they were set to none.
  * After update-modules has been removed, we are not constrained by
calling update-modules anymore in postinst/postrm but we can safely call
depmod to have the dependencies computed.

So, is there anything wrong with the current logic?

Thanks,
Laurentiu



  reply	other threads:[~2013-01-23  8:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 14:58 [PATCH 0/6] Remove obsolete update-modules Laurentiu Palcu
2013-01-17 14:58 ` [PATCH 1/6] modutils-initscripts: improve modutils.sh Laurentiu Palcu
2013-01-17 14:58 ` [PATCH 2/6] orinoco-conf: remove dependencies of update-modules Laurentiu Palcu
2013-01-17 14:58 ` [PATCH 3/6] hostap-conf: " Laurentiu Palcu
2013-01-17 14:58 ` [PATCH 4/6] module.bbclass: do not use update-modules anymore Laurentiu Palcu
2013-01-17 14:58 ` [PATCH 5/6] kernel.bbclass: remove references to update-modules Laurentiu Palcu
2013-01-17 15:26   ` Bruce Ashfield
2013-01-22 20:48   ` Darren Hart
2013-01-23  8:22     ` Laurentiu Palcu [this message]
2013-01-23 16:24       ` Darren Hart
2013-01-17 14:58 ` [PATCH 6/6] bitbake.conf: remove update-modules from DISTRO_FEATURES Laurentiu Palcu
2013-01-18 13:10 ` [PATCH 0/6] Remove obsolete update-modules Richard Purdie

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=50FF9DDB.7040807@intel.com \
    --to=laurentiu.palcu@intel.com \
    --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