All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe MacDonald <joe@deserted.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-selinux][PATCH] README: update the Dependencies area
Date: Wed, 9 Oct 2013 08:21:57 -0400	[thread overview]
Message-ID: <20131009122156.GA5541@deserted.net> (raw)
In-Reply-To: <1381310457-4961-1-git-send-email-Qi.Chen@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]

[[oe] [meta-selinux][PATCH] README: update the Dependencies area] On 13.10.09 (Wed 17:20) Qi.Chen@windriver.com wrote:

> From: Chen Qi <Qi.Chen@windriver.com>
> 
> Add meta-oe to the dependencies as some recipes in meta-selinux may
> require it. Here's a dependency chain:
> 
> ['policycoreutils', 'libselinux', 'swig-native']
> 
> And swig is from meta-oe layer.

I'll take a look at this.  It shouldn't be necessary, meta-selinux
provides its own swig.

meta-selinux/recipes-devtools/swig
├── swig
│   └── 0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch
├── swig_2.0.10.bb
└── swig.inc

Might've crept in during the update last week.

-J.

> 
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
>  README |    7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/README b/README
> index 926d880..987f7ac 100644
> --- a/README
> +++ b/README
> @@ -34,6 +34,13 @@ the Yocto Project website:
>  
>  http://www.yoctoproject.org
>  
> +For some recipes, the meta-oe layer is required:
> +
> +URI: git://github.com/openembedded/meta-oe.git
> +subdirectory: meta-oe
> +branch: master
> +revision: HEAD
> +
>  
>  Maintenance
>  -----------
-- 
-Joe MacDonald.
:wq

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-10-09 12:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09  9:20 [meta-selinux][PATCH] README: update the Dependencies area Qi.Chen
2013-10-09 12:21 ` Joe MacDonald [this message]
2013-10-10  6:10   ` ChenQi

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=20131009122156.GA5541@deserted.net \
    --to=joe@deserted.net \
    --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.