From: akuster <akuster@mvista.com>
To: Mark Hatle <mark.hatle@windriver.com>, Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
openembedded-devel@lists.openembedded.org,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: libpcap-ng
Date: Mon, 28 Jul 2014 17:28:49 -0700 [thread overview]
Message-ID: <53D6EAC1.2030802@mvista.com> (raw)
In-Reply-To: <53D65F40.7010701@windriver.com>
On 07/28/2014 07:33 AM, Mark Hatle wrote:
> 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.
I think core libcap-ng recipe belongs in a common layer and not
maintained in two places.
>> 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.
Well when a security package like 'snort' and maybe others are in other
locations, I can see why meta-security won't be very useful.
It was just a random collection of
> security-like packages, some worked, some didn't.
Hopefully that will change.
- Armin
>
> 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-29 0:28 UTC|newest]
Thread overview: 5+ 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-28 14:33 ` libpcap-ng Mark Hatle
2014-07-29 0:28 ` akuster [this message]
2014-07-29 0:41 ` 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=53D6EAC1.2030802@mvista.com \
--to=akuster@mvista.com \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox