On Mon, Jul 28, 2014 at 5:28 PM, akuster 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
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 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
On 7/25/14, 10:02 PM, Khem Raj wrote:
On Fri, Jul 25, 2014 at 3:45 PM, akuster 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
On Fri, Jul 25, 2014 at 3:45 PM, akuster 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 me
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
--
___
Openembedded-core mailing list
Openembedded-core@lists.openem
