From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: meta-oe and yocto-check-layer
Date: Tue, 25 Sep 2018 22:19:34 +1200 [thread overview]
Message-ID: <13146483.nmZ70cjRe6@localhost.localdomain> (raw)
In-Reply-To: <CAP71WjzB-xkVAnLOBd0jLdKXTh8B87dpHiQUvGhhzm8Q2fNzXQ@mail.gmail.com>
On Tuesday, 25 September 2018 9:43:43 PM NZST Nicolas Dechesne wrote:
> Running the compliance script on meta-oe turned out to be an
> interesting exercise ;)
>
> I have found several issues, which I have mentioned in a few different
> threads, so I will summary here.
>
> * oe-core: fix the yocto-check-layer for dependency loop
> * I have the following local commits in meta-oe:
> meta-oe: add meta-python in LAYERDEPENDS (needed for protobuf)
Right, yeah, I noticed that one too a week or so ago and forgot to raise it. I
actually think this needs to be fixed - meta-oe (at least by previous design)
is not supposed to depend upon any other layer than OE-Core. I believe the
dependency is optional though so we should be able to add a PACKAGECONFIG for
it and default it to disabled. Assuming there is no violent objection and
nobody else gets there first, I'll volunteer to make this fix.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2018-09-25 10:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 10:05 meta-oe and yocto-check-layer Nicolas Dechesne
2018-09-24 21:03 ` Paul Eggleton
2018-09-24 21:51 ` akuster808
2018-09-25 6:59 ` Nicolas Dechesne
2018-09-25 9:43 ` Nicolas Dechesne
2018-09-25 10:19 ` Paul Eggleton [this message]
2018-09-25 10:24 ` Martin Jansa
2018-09-25 10:29 ` Martin Jansa
2018-09-25 13:05 ` Nicolas Dechesne
2018-09-25 17:10 ` Martin Jansa
2018-09-25 17:16 ` Nicolas Dechesne
2018-09-25 17:19 ` Khem Raj
2018-09-25 17:20 ` Martin Jansa
2018-09-25 16:47 ` Khem Raj
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=13146483.nmZ70cjRe6@localhost.localdomain \
--to=paul.eggleton@linux.intel.com \
--cc=nicolas.dechesne@linaro.org \
--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.