From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: <yocto@yoctoproject.org>
Subject: "New" Dependencies (was: Re: [meta-selinux][PATCH] Add explicit dependency on layers with recipes we bbappend.)
Date: Thu, 12 Feb 2015 08:35:08 -0500 [thread overview]
Message-ID: <20150212133508.GA21267@mentor.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2411 bytes --]
I thought I'd better follow this up with a semi-separate thread for
anyone who is using meta-selinux and isn't really interested in the
direct follow-ups when I just indicate a patch has been merged.
This went into master and it captures, I think, the implicit
dependencies in the layer right now. It actually casts a wider net than
is required if you're building core-image-selinux, but it does describe
what's currently included in the layer in terms of appends, so it's the
right thing to do.
If you've been working with a smaller set of selinux layers before,
you'll probably see an error like this:
ERROR: Layer 'selinux' depends on layer 'meta-python', but this layer is not enabled in your configuration
ERROR: Layer 'selinux' depends on layer 'networking-layer', but this layer is not enabled in your configuration
ERROR: Layer 'selinux' depends on layer 'openembedded-layer', but this layer is not enabled in your configuration
ERROR: Layer 'selinux' depends on layer 'virtualization-layer', but this layer is not enabled in your configuration
If you don't want to bring in all of these additional layers, my advice
for the short term is to stick with either the 1.7 branch or if you know
you need to work on master, stick with commit 0d270cbd.
-J.
[Re: [meta-selinux][PATCH] Add explicit dependency on layers with recipes we bbappend.] On 15.02.12 (Thu 08:16) Joe MacDonald wrote:
> [[meta-selinux][PATCH] Add explicit dependency on layers with recipes we bbappend.] On 15.02.12 (Thu 04:39) Philip Tricca wrote:
>
> > This is a stop-gap to get meaningful error messages to folks till we get
> > per-layer bbappends implemented.
> >
> > Signed-off-by: Philip Tricca <flihp@twobit.us>
>
> Merged. Thanks Phil.
>
> -J.
>
> > ---
> > conf/layer.conf | 8 +++++++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/conf/layer.conf b/conf/layer.conf
> > index 7af76a1..723f5a8 100644
> > --- a/conf/layer.conf
> > +++ b/conf/layer.conf
> > @@ -13,4 +13,10 @@ BBFILE_PRIORITY_selinux = "5"
> > # cause compatibility issues with other layers
> > LAYERVERSION_selinux = "1"
> >
> > -LAYERDEPENDS_selinux = "core"
> > +LAYERDEPENDS_selinux = " \
> > + core \
> > + meta-python \
> > + networking-layer \
> > + openembedded-layer \
> > + virtualization-layer \
> > +"
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 501 bytes --]
reply other threads:[~2015-02-12 13:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150212133508.GA21267@mentor.com \
--to=joe_macdonald@mentor.com \
--cc=yocto@yoctoproject.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.