Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Cristian Iorga <cristian.iorga@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] wpa-supplicant-2.0: don't exit in pkg_postinst
Date: Wed, 29 Jan 2014 14:06:33 +0100	[thread overview]
Message-ID: <20140129130632.GG24156@piout.net> (raw)
In-Reply-To: <1389879279-28203-1-git-send-email-alexandre.belloni@free-electrons.com>

Ping ?

On Thu, Jan 16, 2014 at 14:34:39 +0100, Alexandre Belloni wrote :
> Exiting explicitly in pkg_postinst makes it impossible to use the
> update-rc.d class in a .bbappend because the link creation is appended
> to the pkg_postinst script.
> 
> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> ---
>  meta/recipes-connectivity/wpa-supplicant/wpa-supplicant-2.0.inc | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant-2.0.inc b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant-2.0.inc
> index ce669a1ffa4f..ba28c6bd4528 100644
> --- a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant-2.0.inc
> +++ b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant-2.0.inc
> @@ -82,9 +82,8 @@ do_install () {
>  
>  pkg_postinst_wpa-supplicant () {
>  	# If we're offline, we don't need to do this.
> -	if [ "x$D" != "x" ]; then
> -		exit 0
> +	if [ "x$D" = "x" ]; then
> +		killall -q -HUP dbus-daemon || true
>  	fi
>  
> -	killall -q -HUP dbus-daemon || true
>  }
> -- 
> 1.8.3.2
> 

-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com


  reply	other threads:[~2014-01-29 13:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 13:34 [PATCH] wpa-supplicant-2.0: don't exit in pkg_postinst Alexandre Belloni
2014-01-29 13:06 ` Alexandre Belloni [this message]
2014-01-29 17:41   ` Richard Purdie
2014-01-29 18:46     ` Alexandre Belloni

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=20140129130632.GG24156@piout.net \
    --to=alexandre.belloni@free-electrons.com \
    --cc=cristian.iorga@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