From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "T.O. Radzy Radzykewycz" <radzy@windriver.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [meta-selinux][PATCH] swig is in meta-oe, remove this copy
Date: Mon, 22 Feb 2016 11:07:54 -0500 [thread overview]
Message-ID: <20160222160754.GC2255@mentor.com> (raw)
In-Reply-To: <CAJTo0LY7D1o9+9mU13DdEnK_h4SjZPX3+jph5A4fXny_HSHuoA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
[Re: [yocto] [meta-selinux][PATCH] swig is in meta-oe, remove this copy] On 16.02.22 (Mon 15:58) Burton, Ross wrote:
>
> On 22 February 2016 at 15:33, Joe MacDonald <Joe_MacDonald@mentor.com> wrote:
>
> I'm also not against removing the local copy (I don't think it adds
> anything to the layer and occasionally causes headaches), but I really
> don't want to make meta-selinux dependent on meta-oe components, so I
> guess I'm voting for keeping it.
>
>
> Luckily it's also in oe-core (meta/recipes-devtools/swig/swig_3.0.8.bb).
And, y'know what? I thought I'd had this very conversation with Armin
regarding it being in meta-security ages back, but since swig was still
in meta-selinux and Radzy mentioned it's also still in meta-oe, I
assumed it must've been some other package duplicated between
meta-selinux and meta-security (libcap-ng, perhaps?).
So with that, let's say my only concern no longer applies. :-)
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2016-02-22 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 22:59 [meta-selinux][PATCH] swig is in meta-oe, remove this copy T.O. Radzy Radzykewycz
2016-02-22 14:40 ` Mark Hatle
2016-02-22 14:51 ` Radzykewycz, T (Radzy)
2016-02-24 17:10 ` Burton, Ross
2016-02-24 17:53 ` Radzykewycz, T (Radzy)
2016-02-28 2:09 ` Philip Tricca
2016-02-22 15:33 ` Joe MacDonald
2016-02-22 15:57 ` Philip Balister
2016-02-22 15:58 ` Burton, Ross
2016-02-22 16:07 ` Joe MacDonald [this message]
2016-02-22 16:19 ` Martin Jansa
2016-02-22 17:55 ` Mark Hatle
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=20160222160754.GC2255@mentor.com \
--to=joe_macdonald@mentor.com \
--cc=radzy@windriver.com \
--cc=ross.burton@intel.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.