From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org,
Christopher Larson <chris_larson@mentor.com>
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Christopher Larson : update-rc.d.bbclass: explicitly dep on initscripts
Date: Mon, 31 Aug 2015 20:41:13 +0200 [thread overview]
Message-ID: <20150831184113.GF2465@jama> (raw)
In-Reply-To: <20150830114819.3628250369@opal.openembedded.org>
[-- Attachment #1: Type: text/plain, Size: 2443 bytes --]
On Sun, Aug 30, 2015 at 11:48:19AM +0000, git@git.openembedded.org wrote:
> Module: openembedded-core.git
> Branch: master
> Commit: 833302761df924bb503cc2ad04ecae1023381f8f
> URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=833302761df924bb503cc2ad04ecae1023381f8f
>
> Author: Christopher Larson <chris_larson@mentor.com>
> Date: Mon Aug 24 15:18:34 2015 -0700
>
> update-rc.d.bbclass: explicitly dep on initscripts
>
> update-rc.d doesn't just want an initscripts package, it wants
> initscripts-functions. In the case where VIRTUAL-RUNTIME_initscripts is set to
> nothing, update-rc.d still needs initscripts-functions to satisfy its runtime
> dependencies. Further, we shouldn't be using a *runtime* virtual in a *build
> time* variable. This should resolve image creation failures with
> configurations without sysv initscripts when a recipe inherits update-rc.d and
> doesn't inherit systemd.
>
> (From OE-Core rev: e6642ae0849e5ac3174c643a7693af25d829d6d1)
Unfortunately this means that I cannot PNBLACKLIST initscripts recipe in
DISTRO which provides own initscripts implementation (which also
provides initscripts-functions).
What's even worse is that I'll have to overlay whole bbclass to get rid
of this dependency :/
Regards,
>
> Signed-off-by: Christopher Larson <chris_larson@mentor.com>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> ---
>
> meta/classes/update-rc.d.bbclass | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/meta/classes/update-rc.d.bbclass b/meta/classes/update-rc.d.bbclass
> index 6a08315..2a0a74a 100644
> --- a/meta/classes/update-rc.d.bbclass
> +++ b/meta/classes/update-rc.d.bbclass
> @@ -1,8 +1,6 @@
> UPDATERCPN ?= "${PN}"
>
> -DEPENDS_append_class-target = " update-rc.d-native update-rc.d"
> -VIRTUAL-RUNTIME_initscripts ?= "initscripts"
> -DEPENDS_append_class-target = " ${VIRTUAL-RUNTIME_initscripts}"
> +DEPENDS_append_class-target = " update-rc.d-native update-rc.d initscripts"
> UPDATERCD = "update-rc.d"
> UPDATERCD_class-cross = ""
> UPDATERCD_class-native = ""
>
> --
> _______________________________________________
> Openembedded-commits mailing list
> Openembedded-commits@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-commits
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next parent reply other threads:[~2015-08-31 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150830114819.3628250369@opal.openembedded.org>
2015-08-31 18:41 ` Martin Jansa [this message]
2015-08-31 18:58 ` [oe-commits] Christopher Larson : update-rc.d.bbclass: explicitly dep on initscripts Christopher Larson
2015-08-31 19:12 ` Khem Raj
2015-08-31 19:45 ` Christopher Larson
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=20150831184113.GF2465@jama \
--to=martin.jansa@gmail.com \
--cc=chris_larson@mentor.com \
--cc=openembedded-commits@lists.openembedded.org \
--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