summaryrefslogtreecommitdiffstats
path: root/meta/recipes-support/gnupg
diff options
context:
space:
mode:
authorAndré Draszik <git@andred.net>2019-11-07 15:36:39 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-11-10 14:06:10 +0000
commitb3271b42c31e65b4f942c2063ffd59f9c855c32d (patch)
tree28415d27fbeb557d2ce45dca07cc0ed0f1b0d614 /meta/recipes-support/gnupg
parentb30c1f5e46a173221c5ffb248eb9da508f8c446a (diff)
downloadpoky-b3271b42c31e65b4f942c2063ffd59f9c855c32d.tar.gz
libevent: update packaging (one package per shared library)
libevent produces several libraries that might or might not be used in the end. We can prevent those potentially unused libraries from being pulled into a file-system by splitting the individual shared libraries into individual packages. Because this recipe only provides shared libraries which are handled automatically by bitbake (shlibs), there is no need to add the subpackages to the RDEPENDS of PN for backwards compatibility. The packaging process of dependees will simply pull in the sub-packages as runtime dependency as needed. This also how Debian splits this up. While updating the packaging, we can also drop event_rpcgen.py which appears to be a tool for generating rpc bindings, i.e. something that should normally be in -dev. Given Debian doesn't package this at all, and given it actually requires python to run but no runtime dependency is stated at the moment, it would appear that no users of this exist. (From OE-Core rev: d10e8384bfa08d928dfec3a00c59006badfc88ee) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-support/gnupg')
0 files changed, 0 insertions, 0 deletions