From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: wpa-supplicant postinsts failing without sysvinit in DISTRO_FEATURES
Date: Fri, 12 Apr 2013 16:43:35 +0200 [thread overview]
Message-ID: <20130412144335.GR2477@jama> (raw)
In-Reply-To: <CAJTo0LayWKMpxzsX4t67LepAg3AjhJXWtQvoU8-NVG5Qi5eTpA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
On Fri, Apr 12, 2013 at 03:24:57PM +0100, Burton, Ross wrote:
> On 12 April 2013 15:20, Martin Jansa <martin.jansa@gmail.com> wrote:
> > oe-core/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant-2.0.inc
> >
> > defines pkg_postinst_wpa-supplicant
> > with:
> > if [ "x$DBUSPID" != "x" ]; then
> > /etc/init.d/dbus-1 reload || true
> > fi
> >
> > and /etc/init.d/dbus-1 is missing without sysvinit in DISTRO_FEATURES
> >
> > Thanks to "true" it doesn't fail completely, but if the goal is no
> > warnings in images then errors should be fixed too :)
>
> We're going to see stuff like this a lot - clearly we need some
> abstraction over this. One-off for dbus, or a general-purpose small
> abstraction over invoking systemctl or init scripts?
I have noticed this when testing upgrade paths, but general-purpose
abstraction will became quite complicated in images which have both
sysvinit and systemd scripts (I guess that checking which init is
running will be needed to decide if /etc/init.d/foo or systemctl should be
called :/).
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-04-12 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 14:20 wpa-supplicant postinsts failing without sysvinit in DISTRO_FEATURES Martin Jansa
2013-04-12 14:21 ` Martin Jansa
2013-04-12 14:24 ` Burton, Ross
2013-04-12 14:43 ` Martin Jansa [this message]
2013-04-12 14:52 ` Burton, Ross
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=20130412144335.GR2477@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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