From: Patrick Ohly <patrick.ohly@intel.com>
To: openembedded-devel@lists.openembedded.org
Cc: Max Krummenacher <max.krummenacher@toradex.com>
Subject: Re: [meta-oe][PATCH v2][master-next 0/4] python-m2crypto now rdepend on python-typing
Date: Wed, 15 Feb 2017 09:07:40 +0100 [thread overview]
Message-ID: <1487146060.13854.371.camel@intel.com> (raw)
In-Reply-To: <1487108941-20285-1-git-send-email-max.krummenacher@toradex.com>
On Tue, 2017-02-14 at 22:48 +0100, Max Krummenacher wrote:
> For native packages the rdepends do not get automatically installed in the recipe
> specific sysroot.
I'm still not certain whether that RDEPENDS problem is intentional or a
bug which needs to be fixed - see "[OE-core] Does recipe specific
sysrooot (or whatelse in current oe) break native dependencies?"
I don't know how long it might take to resolve this, nor how urgent this
problem is for you, therefore I don't have an opinion whether merging a
(temporary?) workaround is better than waiting.
--
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.
next prev parent reply other threads:[~2017-02-15 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 21:48 [meta-oe][PATCH v2][master-next 0/4] python-m2crypto now rdepend on python-typing Max Krummenacher
2017-02-14 21:48 ` [meta-oe][PATCH v2][master-next 1/4] python-m2crypto: " Max Krummenacher
2017-02-14 21:48 ` [meta-oe][PATCH v2][master-next 2/4] crda: add depends on python-typing-native Max Krummenacher
2017-02-14 21:49 ` [meta-oe][PATCH v2][master-next 3/4] pywbem: " Max Krummenacher
2017-02-14 21:49 ` [meta-oe][PATCH v2][master-next 4/4] openlmi-tools: remove blacklist Max Krummenacher
2017-02-15 8:07 ` Patrick Ohly [this message]
2017-02-15 8:36 ` [meta-oe][PATCH v2][master-next 0/4] python-m2crypto now rdepend on python-typing Max Krummenacher
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=1487146060.13854.371.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=max.krummenacher@toradex.com \
--cc=openembedded-devel@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.