From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] systemd: set INHIBIT_UPDATERCD_BBCLASS without sysvinit in features
Date: Thu, 04 Apr 2013 17:46:48 +0100 [thread overview]
Message-ID: <1365094008.6526.115.camel@ted> (raw)
In-Reply-To: <1365093733-31674-1-git-send-email-Martin.Jansa@gmail.com>
On Thu, 2013-04-04 at 18:42 +0200, Martin Jansa wrote:
> * fixes udev configure in run-postinsts failing with:
> update-rc.d: /etc/init.d/systemd-udev: file does not exist
> because systemd-udev is installed only with sysvinit in features
> but update-rc.d was always called from PN postinst
>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> meta/recipes-core/systemd/systemd_199.bb | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/meta/recipes-core/systemd/systemd_199.bb b/meta/recipes-core/systemd/systemd_199.bb
> index ba1d133..e574548 100644
> --- a/meta/recipes-core/systemd/systemd_199.bb
> +++ b/meta/recipes-core/systemd/systemd_199.bb
> @@ -239,6 +239,12 @@ INITSCRIPT_PACKAGES = "udev"
> INITSCRIPT_NAME_udev = "systemd-udevd"
> INITSCRIPT_PARAMS_udev = "start 03 S ."
>
> +python __anonymous() {
> + features = d.getVar("DISTRO_FEATURES", True).split()
> + if "sysvinit" not in features:
> + d.setVar("INHIBIT_UPDATERCD_BBCLASS", "1")
> +}
> +
> # TODO:
> # u-a for runlevel and telinit
Would this make sense to be in systemd.bbclass?
Cheers,
Richard
next prev parent reply other threads:[~2013-04-04 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 16:42 [PATCH 1/2] systemd: set INHIBIT_UPDATERCD_BBCLASS without sysvinit in features Martin Jansa
2013-04-04 16:42 ` [PATCH 2/2] dbus: " Martin Jansa
2013-04-04 16:46 ` Richard Purdie [this message]
2013-04-04 16:55 ` [PATCH 1/2] systemd: " Martin Jansa
2013-04-04 22:38 ` Richard Purdie
2013-04-08 19:03 ` Martin Jansa
2013-04-16 15:11 ` 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=1365094008.6526.115.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.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