* libpcap-ng
@ 2014-07-25 22:45 akuster
2014-07-26 3:02 ` [OE-core] libpcap-ng Khem Raj
0 siblings, 1 reply; 9+ messages in thread
From: akuster @ 2014-07-25 22:45 UTC (permalink / raw)
To: yocto@yoctoproject.org, OE-core, jackie.huang, Mark Hatle
Hello all,
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?
regards,
Armin
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: libpcap-ng
2014-07-25 22:45 libpcap-ng akuster
@ 2014-07-26 3:02 ` Khem Raj
0 siblings, 0 replies; 9+ messages in thread
From: Khem Raj @ 2014-07-26 3:02 UTC (permalink / raw)
To: akuster; +Cc: yocto@yoctoproject.org, OE-core
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,
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [OE-core] libpcap-ng
@ 2014-07-26 3:02 ` Khem Raj
0 siblings, 0 replies; 9+ messages in thread
From: Khem Raj @ 2014-07-26 3:02 UTC (permalink / raw)
To: akuster; +Cc: yocto@yoctoproject.org, OE-core
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,
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: libpcap-ng
2014-07-26 3:02 ` [OE-core] libpcap-ng Khem Raj
@ 2014-07-28 14:33 ` Mark Hatle
-1 siblings, 0 replies; 9+ messages in thread
From: Mark Hatle @ 2014-07-28 14:33 UTC (permalink / raw)
To: Khem Raj, akuster; +Cc: yocto@yoctoproject.org, OE-core
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [OE-core] libpcap-ng
@ 2014-07-28 14:33 ` Mark Hatle
0 siblings, 0 replies; 9+ messages in thread
From: Mark Hatle @ 2014-07-28 14:33 UTC (permalink / raw)
To: Khem Raj, akuster; +Cc: yocto@yoctoproject.org, OE-core
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: libpcap-ng
2014-07-28 14:33 ` [OE-core] libpcap-ng Mark Hatle
@ 2014-07-29 0:28 ` akuster
-1 siblings, 0 replies; 9+ messages in thread
From: akuster @ 2014-07-29 0:28 UTC (permalink / raw)
To: Mark Hatle, Khem Raj; +Cc: yocto@yoctoproject.org, openembedded-devel, OE-core
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [OE-core] libpcap-ng
@ 2014-07-29 0:28 ` akuster
0 siblings, 0 replies; 9+ messages in thread
From: akuster @ 2014-07-29 0:28 UTC (permalink / raw)
To: Mark Hatle, Khem Raj; +Cc: yocto@yoctoproject.org, openembedded-devel, OE-core
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: libpcap-ng
2014-07-29 0:28 ` [OE-core] libpcap-ng akuster
@ 2014-07-29 0:41 ` Khem Raj
-1 siblings, 0 replies; 9+ messages in thread
From: Khem Raj @ 2014-07-29 0:41 UTC (permalink / raw)
To: akuster; +Cc: yocto@yoctoproject.org, openembeded-devel, OE-core
On Mon, Jul 28, 2014 at 5:28 PM, akuster <akuster@mvista.com> wrote:
>>>
>>> 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.
yes meta-oe is kind of extended common layer besides oe-core, if it
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 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.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [OE-core] libpcap-ng
@ 2014-07-29 0:41 ` Khem Raj
0 siblings, 0 replies; 9+ messages in thread
From: Khem Raj @ 2014-07-29 0:41 UTC (permalink / raw)
To: akuster; +Cc: yocto@yoctoproject.org, openembeded-devel, OE-core
On Mon, Jul 28, 2014 at 5:28 PM, akuster <akuster@mvista.com> wrote:
>>>
>>> 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.
yes meta-oe is kind of extended common layer besides oe-core, if it
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 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.
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2014-07-29 0:41 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 ` libpcap-ng Mark Hatle
2014-07-28 14:33 ` [OE-core] libpcap-ng 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
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.