From: Mark Hatle <mark.hatle@windriver.com>
To: Khem Raj <raj.khem@gmail.com>, akuster <akuster@mvista.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: libpcap-ng
Date: Mon, 28 Jul 2014 09:33:36 -0500 [thread overview]
Message-ID: <53D65F40.7010701@windriver.com> (raw)
In-Reply-To: <CAMKF1son3T9fsuF9X0Px4hirfk7Ezguy4s5Zit6-0JvfmXDV5A@mail.gmail.com>
On 7/25/14, 10:02 PM, Khem Raj wrote:
> On Fri, Jul 25, 2014 at 3:45 PM, akuster <akuster@mvista.com> wrote:
>> Meta-security and Meta-selinux both have libcap-ng. Instead of maintaining
>> the same package in both places, can we get it into OE where libcap resides?
>
> I think at very least you can propose it for meta-oe if not or-core.
> But I also wonder why meta-selinux is not a sub-layer under
> meta-security,
>
meta-selinux existed first... no other reason.
The last time I looked at meta-security (well over a year ago), it wasn't
terribly useful. It was just a random collection of security-like packages,
some worked, some didn't.
If it has grown since then to be more of a cohesive set of packages, then
meta-selinux being part of it may make sense.
--Mark
WARNING: multiple messages have this Message-ID (diff)
From: Mark Hatle <mark.hatle@windriver.com>
To: Khem Raj <raj.khem@gmail.com>, akuster <akuster@mvista.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] libpcap-ng
Date: Mon, 28 Jul 2014 09:33:36 -0500 [thread overview]
Message-ID: <53D65F40.7010701@windriver.com> (raw)
In-Reply-To: <CAMKF1son3T9fsuF9X0Px4hirfk7Ezguy4s5Zit6-0JvfmXDV5A@mail.gmail.com>
On 7/25/14, 10:02 PM, Khem Raj wrote:
> On Fri, Jul 25, 2014 at 3:45 PM, akuster <akuster@mvista.com> wrote:
>> Meta-security and Meta-selinux both have libcap-ng. Instead of maintaining
>> the same package in both places, can we get it into OE where libcap resides?
>
> I think at very least you can propose it for meta-oe if not or-core.
> But I also wonder why meta-selinux is not a sub-layer under
> meta-security,
>
meta-selinux existed first... no other reason.
The last time I looked at meta-security (well over a year ago), it wasn't
terribly useful. It was just a random collection of security-like packages,
some worked, some didn't.
If it has grown since then to be more of a cohesive set of packages, then
meta-selinux being part of it may make sense.
--Mark
next prev parent reply other threads:[~2014-07-28 14:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 22:45 libpcap-ng akuster
2014-07-26 3:02 ` libpcap-ng Khem Raj
2014-07-26 3:02 ` [OE-core] libpcap-ng Khem Raj
2014-07-28 14:33 ` Mark Hatle [this message]
2014-07-28 14:33 ` Mark Hatle
2014-07-29 0:28 ` libpcap-ng akuster
2014-07-29 0:28 ` [OE-core] libpcap-ng akuster
2014-07-29 0:41 ` libpcap-ng Khem Raj
2014-07-29 0:41 ` [OE-core] libpcap-ng 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=53D65F40.7010701@windriver.com \
--to=mark.hatle@windriver.com \
--cc=akuster@mvista.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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.