libpcap-ng
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
Quoted 2 lines · akuster
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,
Quoted 8 lines · Khem Raj
Quoted 2 lines · akuster
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
Quoted 8 lines · Mark Hatle
Quoted 7 lines · Khem Raj
Quoted 4 lines · akuster
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.
Quoted 9 lines
Quoted 3 lines
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
Quoted 1 line
security-like packages, some worked, some didn't.
Hopefully that will change.
- Armin
Quoted 5 lines
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
Quoted 6 lines · akuster
Quoted 2 lines
Quoted 2 lines
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,
Quoted 23 lines
Quoted 11 lines
Quoted 5 lines
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
Quoted 2 lines
security-like packages, some worked, some didn't.
Hopefully that will change.