Date
1 - 4 of 4
[OE-core] libpcap-ng
On Fri, Jul 25, 2014 at 3:45 PM, akuster <akuster@...> wrote:
But I also wonder why meta-selinux is not a sub-layer under
meta-security,
Meta-security and Meta-selinux both have libcap-ng. Instead of maintainingI think at very least you can propose it for meta-oe if not or-core.
the same package in both places, can we get it into OE where libcap resides?
But I also wonder why meta-selinux is not a sub-layer under
meta-security,
Mark Hatle <mark.hatle@...>
On 7/25/14, 10:02 PM, Khem Raj wrote:
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
On Fri, Jul 25, 2014 at 3:45 PM, akuster <akuster@...> wrote:meta-selinux existed first... no other reason.Meta-security and Meta-selinux both have libcap-ng. Instead of maintainingI think at very least you can propose it for meta-oe if not or-core.
the same package in both places, can we get it into OE where libcap resides?
But I also wonder why meta-selinux is not a sub-layer under
meta-security,
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
On 07/28/2014 07:33 AM, Mark Hatle wrote:
It was just a random collection of
- Armin
On 7/25/14, 10:02 PM, Khem Raj wrote:I think core libcap-ng recipe belongs in a common layer and not maintained in two places.On Fri, Jul 25, 2014 at 3:45 PM, akuster <akuster@...> wrote:Meta-security and Meta-selinux both have libcap-ng. Instead ofI think at very least you can propose it for meta-oe if not or-core.
maintaining
the same package in both places, can we get it into OE where libcap
resides?
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.But I also wonder why meta-selinux is not a sub-layer undermeta-selinux existed first... no other reason.
meta-security,
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.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
On Mon, Jul 28, 2014 at 5:28 PM, akuster <akuster@...> wrote:
can be proven that we can drop libpcap and replace its use completely
with libpcap-ng you might have a better case to include it in oe-core,
yes meta-oe is kind of extended common layer besides oe-core, if it
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.
can be proven that we can drop libpcap and replace its use completely
with libpcap-ng you might have a better case to include it in oe-core,
But I also wonder why meta-selinux is not a sub-layer undermeta-selinux existed first... no other reason.
meta-security,
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.