Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2 v2] libcap-ng: add package 0.7.7
Date: Tue, 25 Aug 2015 08:21:37 -0500	[thread overview]
Message-ID: <55DC6BE1.2020602@windriver.com> (raw)
In-Reply-To: <CAMKF1srfmPb6MAwTuV-jCKi3Z-fbWRv069fJi+uTLu2DCKtwZg@mail.gmail.com>

On 8/24/15 6:41 PM, Khem Raj wrote:
> On Mon, Aug 24, 2015 at 3:27 PM, Mark Hatle <mark.hatle@windriver.com> wrote:
>> I agree BTW that it's the wrong answer to say since it's used in multiple places
>> that it belongs in oe-core.
>>
>> HOWEVER, in this case, I think the use in multiple places is a reasonable
>> justification that it's a commonly used, and potentially core component.
>>
>> Add that that it's implementing posix capabilities.. and I do think it's
>> reasonable to put this -one- in oe-core.  (The key to this, as always, is that
>> these things need to be looked at individually to see if it's reasonable.)
>>
>> Anyway, this ONE has my vote to go into oe-core, based on the usage patterns I
>> routinely see.. and that fact that I believe we have people willing to step in
>> and upgrade/maintain it moving forward.
> 
> you have it your way, the patch has been pushed into OE-Core so
> further discussions is moot from here on, I wish we wait for
> discussions to finish for little we discuss on patches now a days.
> anyway for this
> but on debian I see there aren't many reverse deps given thousands of
> debian packages its only needed by handful
> 
> libcap-ng0

I find it heavily used by security and auditing software.  Specifically selinux
(and related auditing), dbus, keyrings, etc..  This is why I think it was good
for oe-core.  But as you said point is moot now.

(I don't develop with debian at all, but from the list below, it looks like that
set of debian doesn't use support or use an LSM items, like selinux...)

--Mark

> Reverse Depends:
>  qemu-system-common
>  libvirt0
>  libvirt-bin
>  suricata
>  libcap-ng-utils
>  ladvd
>  heimdal-kdc
>  audispd-plugins
>  smartmontools
>  qemu-system-common
>  libvirt0
>  libvirt-bin
>  libcap-ng-dev
>  irqbalance
>  gnome-keyring
>  dbus-1-dbg
>  dbus
> 
> That doesn't look much core component to me to be frank, But yes when
> one needs it in his own setup then it becomes pretty core. I can site
> you an example of many,  RDK depend on yajl its found in multiple
> layers too but we happily take it from meta-oe because we want to
> respect the layer boundaries.
> 



      reply	other threads:[~2015-08-25 13:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21  5:38 [PATCH 0/2 v2] libcap-ng, swig: add packages wenzong.fan
2015-08-21  5:38 ` [PATCH 1/2 v2] swig: add package 3.0.6 wenzong.fan
2015-08-21  5:38 ` [PATCH 2/2 v2] libcap-ng: add package 0.7.7 wenzong.fan
2015-08-21  7:25   ` Khem Raj
2015-08-22  0:55     ` Randy MacLeod
2015-08-22  1:14       ` Andre McCurdy
2015-08-24 22:30         ` Mark Hatle
2015-08-24 22:53         ` Randy MacLeod
2015-08-24 23:48           ` Khem Raj
2015-08-22  1:36       ` Khem Raj
2015-08-24 22:27     ` Mark Hatle
2015-08-24 23:41       ` Khem Raj
2015-08-25 13:21         ` Mark Hatle [this message]

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=55DC6BE1.2020602@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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