From: Patrick Ohly <patrick.ohly@intel.com>
To: Joe Slater <jslater@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] systemd-compat-units: do not inherit allarch
Date: Thu, 25 Aug 2016 09:01:10 +0200 [thread overview]
Message-ID: <1472108470.396.1.camel@intel.com> (raw)
In-Reply-To: <1471903951-2925-1-git-send-email-jslater@windriver.com>
On Mon, 2016-08-22 at 15:12 -0700, Joe Slater wrote:
> Even though we are just a script, we do depend on
> systemd being on the target and need an RDEPENDS
> which means we cannot also be allarch.
>
> Signed-off-by: Joe Slater <jslater@windriver.com>
> ---
> meta/recipes-core/systemd/systemd-compat-units.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/systemd/systemd-compat-units.bb b/meta/recipes-core/systemd/systemd-compat-units.bb
> index f246e83..421fc06 100644
> --- a/meta/recipes-core/systemd/systemd-compat-units.bb
> +++ b/meta/recipes-core/systemd/systemd-compat-units.bb
> @@ -9,7 +9,7 @@ DEPENDS = "systemd-systemctl-native"
>
> S = "${WORKDIR}"
>
> -inherit allarch distro_features_check
> +inherit distro_features_check
+1 from me. The alternative solution would be to add
"systemd-compat-units->systemd" to SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS in
meta/conf/layer.conf, but that's more complicated and probably not worth
it.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
prev parent reply other threads:[~2016-08-25 7:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 22:12 [PATCH 1/1] systemd-compat-units: do not inherit allarch Joe Slater
2016-08-25 7:01 ` Patrick Ohly [this message]
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=1472108470.396.1.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=jslater@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.