On Mon, Aug 24, 2015 at 3:27 PM, Mark Hatle <[email protected]> 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 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. -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
