libcap-ng, swig: add packages
v2 cover libcap-ng, swig: add packages
From: Wenzong Fan <[email protected]>
V2 changes:
* add swig 3.0.6 which the latest version from meta-oe
The following changes since commit a01a33b17861c227c1c16fbc2d819d86fb9bf893:
linux-yocto-3.14: Update to branch HEADs (2015-08-20 15:17:01 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib wenzong/libcap-ng
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=wenzong/libcap-ng
Wenzong Fan (2):
swig: add package 3.0.6
libcap-ng: add package 0.7.7
meta/recipes-devtools/swig/swig.inc | 63 ++++++++++++++++++++ ...lf-exe-for-swig-swiglib-on-non-Win32-plat.patch | 69 ++++++++++++++++++++++ ...nfigure-use-pkg-config-for-pcre-detection.patch | 64 ++++++++++++++++++++ meta/recipes-devtools/swig/swig_3.0.6.bb | 8 +++ .../libcap-ng/libcap-ng/python.patch | 58 ++++++++++++++++++ meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb | 39 ++++++++++++ 6 files changed, 301 insertions(+) create mode 100644 meta/recipes-devtools/swig/swig.inc create mode 100644 meta/recipes-devtools/swig/swig/0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch create mode 100644 meta/recipes-devtools/swig/swig/0001-configure-use-pkg-config-for-pcre-detection.patch create mode 100644 meta/recipes-devtools/swig/swig_3.0.6.bb create mode 100644 meta/recipes-support/libcap-ng/libcap-ng/python.patch create mode 100644 meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb
Signature · 1 line
1.9.1
PATCH v2 1/2 swig: add package 3.0.6
From: Wenzong Fan <[email protected]>
Ackage from meta-oe to oe-core:
meta-oe commit: 9cc54e10efa5ca70d9980f833a8e5a310e5ad21d
It's required for libcap-ng to build python bindings.
With adding it to oe-core, the copies from following layers could be removed:
* meta-oe, meta-selinux, meta-intel-iot-middleware ...
--- meta/recipes-devtools/swig/swig.inc | 63 ++++++++++++++++++++ ...lf-exe-for-swig-swiglib-on-non-Win32-plat.patch | 69 ++++++++++++++++++++++ ...nfigure-use-pkg-config-for-pcre-detection.patch | 64 ++++++++++++++++++++ meta/recipes-devtools/swig/swig_3.0.6.bb | 8 +++ 4 files changed, 204 insertions(+) create mode 100644 meta/recipes-devtools/swig/swig.inc create mode 100644 meta/recipes-devtools/swig/swig/0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch create mode 100644 meta/recipes-devtools/swig/swig/0001-configure-use-pkg-config-for-pcre-detection.patch create mode 100644 meta/recipes-devtools/swig/swig_3.0.6.bb
meta/recipes-devtools/swig/swig.inc new file +63 -0
@@ -0,0 +1,63 @@ +DESCRIPTION = "SWIG - Simplified Wrapper and Interface Generator" +HOMEPAGE = "http://swig.sourceforge.net/" +LICENSE = "BSD & GPLv3" +LIC_FILES_CHKSUM = "file://LICENSE;md5=e7807a6282784a7dde4c846626b08fc6 \ + file://LICENSE-GPL;md5=d32239bcb673463ab874e80d47fae504 \ + file://LICENSE-UNIVERSITIES;md5=8ce9dcc8f7c994de4a408b205c72ba08" + +SECTION = "devel" + +DEPENDS = "libpcre python" + +SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/${BPN}-${PV}.tar.gz" + +inherit autotools pythonnative + +EXTRA_OECONF = " \ + --with-python=${PYTHON} \ + --without-allegrocl \ + --without-android \ + --without-boost \ + --without-chicken \ + --without-clisp \ + --without-csharp \ + --without-d \ + --without-gcj \ + --without-go \ + --without-guile \ + --without-java \ + --without-lua \ + --without-mzscheme \ + --without-ocaml \ + --without-octave \ + --without-perl5 \ + --without-pike \ + --without-php \ + --without-python3 \ + --without-r \ + --without-ruby \ + --without-tcl \ +" + +BBCLASSEXTEND = "native nativesdk" + +do_configure() { + install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.guess ${S}/Tools/config + install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.sub ${S}/Tools/config + install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.guess ${S} + install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.sub ${S} + oe_runconf +} + +do_install_append_class-nativesdk() { + cd ${D}${bindir} + ln -s swig swig2.0 +} + +def swiglib_relpath(d): + swiglib = d.getVar('datadir', True) + "/" + d.getVar('BPN', True) + "/" + d.getVar('PV', True) + return os.path.relpath(swiglib, d.getVar('bindir', True)) + +do_install_append_class-native() { + create_wrapper ${D}${bindir}/swig SWIG_LIB='`dirname $''realpath`'/${@swiglib_relpath(d)} +}
meta/recipes-devtools/swig/swig/0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch new file +69 -0
69 lines not on this page · raw message
meta/recipes-devtools/swig/swig/0001-configure-use-pkg-config-for-pcre-detection.patch new file +64 -0
64 lines not on this page · raw message
meta/recipes-devtools/swig/swig_3.0.6.bb new file +8 -0
@@ -0,0 +1,8 @@ +require ${BPN}.inc + +SRC_URI += "file://0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch \ + file://0001-configure-use-pkg-config-for-pcre-detection.patch \ + " +SRC_URI[md5sum] = "df43ae271642bcfa61c1e59f970f9963" +SRC_URI[sha256sum] = "c67f63ea11956106e4cda66416d5020330dc4ce2ee45057d39a9494ce33eca05" +
Signature · 1 line
1.9.1
PATCH v2 2/2 libcap-ng: add package 0.7.7
In reply to [email protected]From: Wenzong Fan <[email protected]>
Pull package from meta-oe to oe-core:
meta-oe commit: bce4dba5546480c8e43c6442959ac7d0a4ef32f6
The libcap-ng library is intended to make programming with posix capabilities much easier than the traditional libcap library.
It's not a replacement to libcap, it provides different library (libcap-ng.so) while packages explicitly look for libcap.so. It could be used by qemu, util-linux, libvirt, audit ...
With adding it to oe-core, the copies from following layers could be removed:
* meta-oe, meta-selinux, meta-security-framework ...
--- .../libcap-ng/libcap-ng/python.patch | 58 ++++++++++++++++++++++ meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb | 39 +++++++++++++++ 2 files changed, 97 insertions(+) create mode 100644 meta/recipes-support/libcap-ng/libcap-ng/python.patch create mode 100644 meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb
meta/recipes-support/libcap-ng/libcap-ng/python.patch new file +58 -0
@@ -0,0 +1,58 @@ +From b01bb2694f66cd981e6d61523433dc3eb5ed32f2 Mon Sep 17 00:00:00 2001 +From: Li xin <[email protected]> +Date: Sat, 18 Jul 2015 23:03:30 +0900 +Subject: [PATCH] configure.ac - Avoid an incorrect check for python. + Makefile.am - avoid hard coded host include paths. + +Upstream-Status: pending + +Signed-off-by: Mark Hatle <[email protected]> +Signed-off-by: Li Xin <[email protected]> +--- + bindings/python/Makefile.am | 3 ++- + configure.ac | 15 ++------------- + 2 files changed, 4 insertions(+), 14 deletions(-) + +diff --git a/bindings/python/Makefile.am b/bindings/python/Makefile.am +index 82b9bb8..f9fe7a8 100644 +--- a/bindings/python/Makefile.am ++++ b/bindings/python/Makefile.am +@@ -23,7 +23,8 @@ SUBDIRS = test + CONFIG_CLEAN_FILES = *.loT *.rej *.orig + AM_CFLAGS = -fPIC -DPIC + PYLIBVER ?= python$(PYTHON_VERSION) +-AM_CPPFLAGS = -I. -I$(top_builddir) -I@PYINCLUDEDIR@ ++PYINC ?= /usr/include/$(PYLIBVER) ++AM_CPPFLAGS = -I. -I$(top_builddir) -I$(PYINC) + LIBS = $(top_builddir)/src/libcap-ng.la + SWIG_FLAGS = -python + SWIG_INCLUDES = ${AM_CPPFLAGS} +diff --git a/configure.ac b/configure.ac +index 1d777d5..9d90f64 100644 +--- a/configure.ac ++++ b/configure.ac +@@ -123,19 +123,8 @@ if test x$use_python = xno ; then + else + AC_MSG_RESULT(testing) + AM_PATH_PYTHON +-PYINCLUDEDIR=`python${am_cv_python_version} -c "from distutils import sysconfig; print(sysconfig.get_config_var('INCLUDEPY'))"` +-if test -f ${PYINCLUDEDIR}/Python.h ; then +- python_found="yes" +- AC_SUBST(PYINCLUDEDIR) +- AC_MSG_NOTICE(Python bindings will be built) +-else +- python_found="no" +- if test x$use_python = xyes ; then +- AC_MSG_ERROR([Python explicitly required and python headers found]) +- else +- AC_MSG_WARN("Python headers not found - python bindings will not be made") +- fi +-fi ++python_found="yes" ++AC_MSG_NOTICE(Python bindings will be built) + fi + AM_CONDITIONAL(HAVE_PYTHON, test ${python_found} = "yes") + +-- +1.8.4.2 +
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +39 -0
@@ -0,0 +1,39 @@ +SUMMARY = "An alternate posix capabilities library" +DESCRIPTION = "The libcap-ng library is intended to make programming \ +with POSIX capabilities much easier than the traditional libcap library." +HOMEPAGE = "http://freecode.com/projects/libcap-ng" +SECTION = "base" +LICENSE = "GPLv2+ & LGPLv2.1+" +LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \ + file://COPYING.LIB;md5=e3eda01d9815f8d24aae2dbd89b68b06" + +SRC_URI = "http://people.redhat.com/sgrubb/libcap-ng/libcap-ng-${PV}.tar.gz \ + file://python.patch" + +inherit lib_package autotools pythonnative + +SRC_URI[md5sum] = "3d7d126b29e2869a0257c17c8b0d9b2e" +SRC_URI[sha256sum] = "615549ce39b333f6b78baee0c0b4ef18bc726c6bf1cca123dfd89dd963f6d06b" + +DEPENDS += "swig-native python" + +EXTRA_OECONF += "--without-python3" + +EXTRA_OEMAKE += "PYLIBVER='python${PYTHON_BASEVERSION}' PYINC='${STAGING_INCDIR}/${PYLIBVER}'" + +PACKAGES += "${PN}-python" + +FILES_${PN}-dbg += "${libdir}/python${PYTHON_BASEVERSION}/*/.debug" +FILES_${PN}-python = "${libdir}/python${PYTHON_BASEVERSION}" + +BBCLASSEXTEND = "native" + +do_install_append() { + # Moving libcap-ng to base_libdir + if [ ! ${D}${libdir} -ef ${D}${base_libdir} ]; then + mkdir -p ${D}/${base_libdir}/ + mv -f ${D}${libdir}/libcap-ng.so.* ${D}${base_libdir}/ + relpath=${@os.path.relpath("${base_libdir}", "${libdir}")} + ln -sf ${relpath}/libcap-ng.so.0.0.0 ${D}${libdir}/libcap-ng.so + fi +}
Signature · 1 line
1.9.1
Re: [PATCH 2/2 v2] libcap-ng: add package 0.7.7
Quoted 8 lines · On Thu, Aug 20, 2015 at 10:38 PM, <[email protected]> wrote:
From: Wenzong Fan <[email protected]>
Pull package from meta-oe to oe-core:
meta-oe commit:bce4dba5546480c8e43c6442959ac7d0a4ef32f6The libcap-ng library is intended to make programming with posix capabilities much easier than the traditional libcap library.
Quoted 8 lines
It's not a replacement to libcap, it provides different library (libcap-ng.so) while packages explicitly look for libcap.so. It could be used by qemu, util-linux, libvirt, audit ...
With adding it to oe-core, the copies from following layers could be removed:
* meta-oe, meta-selinux, meta-security-framework ...
I am afraid that we are setting a pretext for moving all recipes that are in multiple layers to be eligible for OE-core now. met-oe is common layer for extended recipes, so may be other layers should have been a bit more vigilant and made sure
there requirements were met with whats in meta-oe.
we should ask what core feature does it enable for reference images and machines.
Quoted 126 lines
Signed-off-by Wenzong Fan <[email protected]>--- .../libcap-ng/libcap-ng/python.patch | 58 ++++++++++++++++++++++ meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb | 39 +++++++++++++++ 2 files changed, 97 insertions(+) create mode 100644 meta/recipes-support/libcap-ng/libcap-ng/python.patch create mode 100644 meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bbmeta/recipes-support/libcap-ng/libcap-ng/python.patch new file +58
-0@@ -0,0 +1,58 @@ +From b01bb2694f66cd981e6d61523433dc3eb5ed32f2 Mon Sep 17 00:00:00 2001 +From: Li xin <[email protected]> +Date: Sat, 18 Jul 2015 23:03:30 +0900 +Subject: [PATCH] configure.ac - Avoid an incorrect check for python. + Makefile.am - avoid hard coded host include paths. + +Upstream-Status: pending + +Signed-off-by: Mark Hatle <[email protected]> +Signed-off-by: Li Xin <[email protected]> +--- + bindings/python/Makefile.am | 3 ++- + configure.ac | 15 ++------------- + 2 files changed, 4 insertions(+), 14 deletions(-) + +diff --git a/bindings/python/Makefile.am b/bindings/python/Makefile.am +index 82b9bb8..f9fe7a8 100644 +--- a/bindings/python/Makefile.am ++++ b/bindings/python/Makefile.am +@@ -23,7 +23,8 @@ SUBDIRS = test + CONFIG_CLEAN_FILES = *.loT *.rej *.orig + AM_CFLAGS = -fPIC -DPIC + PYLIBVER ?= python$(PYTHON_VERSION) +-AM_CPPFLAGS = -I. -I$(top_builddir) -I@PYINCLUDEDIR@ ++PYINC ?= /usr/include/$(PYLIBVER) ++AM_CPPFLAGS = -I. -I$(top_builddir) -I$(PYINC) + LIBS = $(top_builddir)/src/libcap-ng.la + SWIG_FLAGS = -python + SWIG_INCLUDES = ${AM_CPPFLAGS} +diff --git a/configure.ac b/configure.ac +index 1d777d5..9d90f64 100644 +--- a/configure.ac ++++ b/configure.ac +@@ -123,19 +123,8 @@ if test x$use_python = xno ; then + else + AC_MSG_RESULT(testing) + AM_PATH_PYTHON +-PYINCLUDEDIR=`python${am_cv_python_version} -c "from distutils import sysconfig; print(sysconfig.get_config_var('INCLUDEPY'))"` +-if test -f ${PYINCLUDEDIR}/Python.h ; then +- python_found="yes" +- AC_SUBST(PYINCLUDEDIR) +- AC_MSG_NOTICE(Python bindings will be built) +-else +- python_found="no" +- if test x$use_python = xyes ; then +- AC_MSG_ERROR([Python explicitly required and python headers found]) +- else +- AC_MSG_WARN("Python headers not found - python bindings will not be made") +- fi +-fi ++python_found="yes" ++AC_MSG_NOTICE(Python bindings will be built) + fi + AM_CONDITIONAL(HAVE_PYTHON, test ${python_found} = "yes") + +-- +1.8.4.2 +meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +39
-1@@ -0,0 +1,39 @@ +SUMMARY = "An alternate posix capabilities library" +DESCRIPTION = "The libcap-ng library is intended to make programming \ +with POSIX capabilities much easier than the traditional libcap library." +HOMEPAGE = "http://freecode.com/projects/libcap-ng" +SECTION = "base" +LICENSE = "GPLv2+ & LGPLv2.1+" +LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \ + file://COPYING.LIB;md5=e3eda01d9815f8d24aae2dbd89b68b06" + +SRC_URI = "http://people.redhat.com/sgrubb/libcap-ng/libcap-ng-${PV}.tar.gz \ + file://python.patch" + +inherit lib_package autotools pythonnative + +SRC_URI[md5sum] = "3d7d126b29e2869a0257c17c8b0d9b2e" +SRC_URI[sha256sum] = "615549ce39b333f6b78baee0c0b4ef18bc726c6bf1cca123dfd89dd963f6d06b" + +DEPENDS += "swig-native python" + +EXTRA_OECONF += "--without-python3" + +EXTRA_OEMAKE += "PYLIBVER='python${PYTHON_BASEVERSION}' PYINC='${STAGING_INCDIR}/${PYLIBVER}'" + +PACKAGES += "${PN}-python" + +FILES_${PN}-dbg += "${libdir}/python${PYTHON_BASEVERSION}/*/.debug" +FILES_${PN}-python = "${libdir}/python${PYTHON_BASEVERSION}" + +BBCLASSEXTEND = "native" + +do_install_append() { + # Moving libcap-ng to base_libdir + if [ ! ${D}${libdir} -ef ${D}${base_libdir} ]; then + mkdir -p ${D}/${base_libdir}/ + mv -f ${D}${libdir}/libcap-ng.so.* ${D}${base_libdir}/ + relpath=${@os.path.relpath("${base_libdir}", "${libdir}")} + ln -sf ${relpath}/libcap-ng.so.0.0.0 ${D}${libdir}/libcap-ng.so + fi +} --1.9.1
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [PATCH 2/2 v2] libcap-ng: add package 0.7.7
Quoted 16 lines · Khem Raj
Quoted 15 lines · On Thu, Aug 20, 2015 at 10:38 PM, <[email protected]> wrote:
From: Wenzong Fan <[email protected]>
Pull package from meta-oe to oe-core:
meta-oe commit:bce4dba5546480c8e43c6442959ac7d0a4ef32f6The libcap-ng library is intended to make programming with posix capabilities much easier than the traditional libcap library.
It's not a replacement to libcap, it provides different library (libcap-ng.so) while packages explicitly look for libcap.so. It could be used by qemu, util-linux, libvirt, audit ...
With adding it to oe-core, the copies from following layers could be removed:
Quoted 7 lines
Quoted 1 line
* meta-oe, meta-selinux, meta-security-framework ...
I am afraid that we are setting a pretext for moving all recipes that are in multiple layers to be eligible for OE-core now. meta-oe is common layer for extended recipes, so may be other layers should have been a bit more vigilant and made sure
there requirements were met with whats in meta-oe.
Meta-oe has far to many recipes for some people to want to include the entire layer:
meta-oe.git $ find meta-oe/ -name "*bb" | wc -l
618
We can certainly use the new whitelist layer filtering to get to a smaller collection of recipes but I'd like to suggest we need to document and maybe design the layer structure
a bit more. There are lots of different opinions about how to split collections of packages in to different layers so unless someone has a dependency-based analysis of all pacakges in all layers, I don't see much point in a long discussion on this topic.
Has the idea of creating a new meta-openembedded layer for widely-used, OS interface libraries been proposed? These 80 recipes could be considered for inclusion:
$ find meta-oe -name "lib*bb" | wc -l 80 but more consideration is probably needed.
In the short term (oe-core-1.9 (now 2.0), I guess we leave things as they are. Sigh...
../Randy
While I'm at it, for reference of layer size:
$ for i in `ls -d meta-*`; do echo -n $i": "; find $i -name "*bb" | wc -l; done meta-efl: 57 meta-filesystems: 16 meta-gnome: 82 meta-gpe: 5 meta-initramfs: 14 meta-multimedia: 51 meta-networking: 115 meta-oe: 618 meta-perl: 30 meta-python: 74 meta-ruby: 4 meta-systemd: 1 meta-webserver: 13 meta-xfce: 67
-----------------------------------------
Quoted 129 lines
we should ask what core feature does it enable for reference images and machines.
Quoted 126 lines
Signed-off-by Wenzong Fan <[email protected]>--- .../libcap-ng/libcap-ng/python.patch | 58 ++++++++++++++++++++++ meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb | 39 +++++++++++++++ 2 files changed, 97 insertions(+)create mode 100644
meta/recipes-support/libcap-ng/libcap-ng/python.patchcreate mode 100644 meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bbmeta/recipes-support/libcap-ng/libcap-ng/python.patch new file +58
-0@@ -0,0 +1,58 @@ +From b01bb2694f66cd981e6d61523433dc3eb5ed32f2 Mon Sep 17 00:00:00 2001 +From: Li xin <[email protected]> +Date: Sat, 18 Jul 2015 23:03:30 +0900 +Subject: [PATCH] configure.ac - Avoid an incorrect check for python. + Makefile.am - avoid hard coded host include paths. + +Upstream-Status: pending + +Signed-off-by: Mark Hatle <[email protected]> +Signed-off-by: Li Xin <[email protected]> +--- + bindings/python/Makefile.am | 3 ++- + configure.ac | 15 ++------------- + 2 files changed, 4 insertions(+), 14 deletions(-) + +diff --git a/bindings/python/Makefile.am b/bindings/python/Makefile.am +index 82b9bb8..f9fe7a8 100644 +--- a/bindings/python/Makefile.am ++++ b/bindings/python/Makefile.am +@@ -23,7 +23,8 @@ SUBDIRS = test + CONFIG_CLEAN_FILES = *.loT *.rej *.orig + AM_CFLAGS = -fPIC -DPIC + PYLIBVER ?= python$(PYTHON_VERSION) +-AM_CPPFLAGS = -I. -I$(top_builddir) -I@PYINCLUDEDIR@ ++PYINC ?= /usr/include/$(PYLIBVER) ++AM_CPPFLAGS = -I. -I$(top_builddir) -I$(PYINC) + LIBS = $(top_builddir)/src/libcap-ng.la + SWIG_FLAGS = -python + SWIG_INCLUDES = ${AM_CPPFLAGS} +diff --git a/configure.ac b/configure.ac +index 1d777d5..9d90f64 100644 +--- a/configure.ac ++++ b/configure.ac +@@ -123,19 +123,8 @@ if test x$use_python = xno ; then + else + AC_MSG_RESULT(testing) + AM_PATH_PYTHON +-PYINCLUDEDIR=`python${am_cv_python_version} -c "from distutils import sysconfig; print(sysconfig.get_config_var('INCLUDEPY'))"` +-if test -f ${PYINCLUDEDIR}/Python.h ; then +- python_found="yes" +- AC_SUBST(PYINCLUDEDIR) +- AC_MSG_NOTICE(Python bindings will be built) +-else +- python_found="no" +- if test x$use_python = xyes ; then +- AC_MSG_ERROR([Python explicitly required and python headers found]) +- else +- AC_MSG_WARN("Python headers not found - python bindings will not be made") +- fi +-fi ++python_found="yes" ++AC_MSG_NOTICE(Python bindings will be built) + fi + AM_CONDITIONAL(HAVE_PYTHON, test ${python_found} = "yes") + +-- +1.8.4.2 +meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +39
-1@@ -0,0 +1,39 @@ +SUMMARY = "An alternate posix capabilities library" +DESCRIPTION = "The libcap-ng library is intended to make programming \ +with POSIX capabilities much easier than the traditional libcap library." +HOMEPAGE = "http://freecode.com/projects/libcap-ng" +SECTION = "base" +LICENSE = "GPLv2+ & LGPLv2.1+" +LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \ + file://COPYING.LIB;md5=e3eda01d9815f8d24aae2dbd89b68b06" + +SRC_URI = "http://people.redhat.com/sgrubb/libcap-ng/libcap-ng-${PV}.tar.gz \ + file://python.patch" + +inherit lib_package autotools pythonnative + +SRC_URI[md5sum] = "3d7d126b29e2869a0257c17c8b0d9b2e" +SRC_URI[sha256sum] = "615549ce39b333f6b78baee0c0b4ef18bc726c6bf1cca123dfd89dd963f6d06b" + +DEPENDS += "swig-native python" + +EXTRA_OECONF += "--without-python3" + +EXTRA_OEMAKE += "PYLIBVER='python${PYTHON_BASEVERSION}' PYINC='${STAGING_INCDIR}/${PYLIBVER}'" + +PACKAGES += "${PN}-python" + +FILES_${PN}-dbg += "${libdir}/python${PYTHON_BASEVERSION}/*/.debug" +FILES_${PN}-python = "${libdir}/python${PYTHON_BASEVERSION}" + +BBCLASSEXTEND = "native" + +do_install_append() { + # Moving libcap-ng to base_libdir + if [ ! ${D}${libdir} -ef ${D}${base_libdir} ]; then + mkdir -p ${D}/${base_libdir}/ + mv -f ${D}${libdir}/libcap-ng.so.* ${D}${base_libdir}/ + relpath=${@os.path.relpath("${base_libdir}", "${libdir}")} + ln -sf ${relpath}/libcap-ng.so.0.0.0 ${D}${libdir}/libcap-ng.so + fi +} --1.9.1
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Signature · 2 lines
# Randy MacLeod. SMTS, Linux, Wind River Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON, Canada, K2K 2W5
Re: [PATCH 2/2 v2] libcap-ng: add package 0.7.7
Quoted 29 lines · Randy MacLeod
Quoted 18 lines · Khem Raj
Quoted 16 lines · On Thu, Aug 20, 2015 at 10:38 PM, <[email protected]> wrote:
From: Wenzong Fan <[email protected]>
Pull package from meta-oe to oe-core:
meta-oe commit:bce4dba5546480c8e43c6442959ac7d0a4ef32f6The libcap-ng library is intended to make programming with posix capabilities much easier than the traditional libcap library.
It's not a replacement to libcap, it provides different library (libcap-ng.so) while packages explicitly look for libcap.so. It could be used by qemu, util-linux, libvirt, audit ...
With adding it to oe-core, the copies from following layers could be removed:
Quoted 8 lines
Quoted 1 line
* meta-oe, meta-selinux, meta-security-framework ...
I am afraid that we are setting a pretext for moving all recipes that are in multiple layers to be eligible for OE-core now. meta-oe is common layer for extended recipes, so may be other layers should have been a bit more vigilant and made sure
there requirements were met with whats in meta-oe.
Quoted 4 lines
Meta-oe has far to many recipes for some people to want to include the entire layer:
meta-oe.git $ find meta-oe/ -name "*bb" | wc -l 618
I typically include most of the meta-oe layers, but I've never really given much thought to how many recipes there are.
Is the concern that parsing too many recipes makes bitbake slow? Or is there another reason why I wouldn't want to include them all?
Quoted 202 lines
We can certainly use the new whitelist layer filtering to get to a smaller collection of recipes but I'd like to suggest we need to document and maybe design the layer structure
a bit more. There are lots of different opinions about how to split collections of packages in to different layers so unless someone has a dependency-based analysis of all pacakges in all layers, I don't see much point in a long discussion on this topic.Has the idea of creating a new meta-openembedded layer for widely-used, OS interface libraries been proposed? These 80 recipes could be considered for inclusion:
$ find meta-oe -name "lib*bb" | wc -l 80 but more consideration is probably needed.In the short term (oe-core-1.9 (now 2.0), I guess we leave things as they are. Sigh...
../Randy
While I'm at it, for reference of layer size:
$ for i in `ls -d meta-*`; do echo -n $i": "; find $i -name "*bb" | wc -l; done meta-efl: 57 meta-filesystems: 16 meta-gnome: 82 meta-gpe: 5 meta-initramfs: 14 meta-multimedia: 51 meta-networking: 115 meta-oe: 618 meta-perl: 30 meta-python: 74 meta-ruby: 4 meta-systemd: 1 meta-webserver: 13 meta-xfce: 67-----------------------------------------
Quoted 139 lines
we should ask what core feature does it enable for reference images and machines.
Quoted 136 lines
Signed-off-by Wenzong Fan <[email protected]>--- .../libcap-ng/libcap-ng/python.patch | 58 ++++++++++++++++++++++ meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb | 39 +++++++++++++++ 2 files changed, 97 insertions(+)create mode 100644
meta/recipes-support/libcap-ng/libcap-ng/python.patch
create mode 100644 meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bbmeta/recipes-support/libcap-ng/libcap-ng/python.patch new file +38
-0@@ -0,0 +1,58 @@ +From b01bb2694f66cd981e6d61523433dc3eb5ed32f2 Mon Sep 17 00:00:00 2001 +From: Li xin <[email protected]> +Date: Sat, 18 Jul 2015 23:03:30 +0900 +Subject: [PATCH] configure.ac - Avoid an incorrect check for python. + Makefile.am - avoid hard coded host include paths. + +Upstream-Status: pending + +Signed-off-by: Mark Hatle <[email protected]> +Signed-off-by: Li Xin <[email protected]> +--- + bindings/python/Makefile.am | 3 ++- + configure.ac | 15 ++------------- + 2 files changed, 4 insertions(+), 14 deletions(-) + +diff --git a/bindings/python/Makefile.am b/bindings/python/Makefile.am +index 82b9bb8..f9fe7a8 100644 +--- a/bindings/python/Makefile.am ++++ b/bindings/python/Makefile.am +@@ -23,7 +23,8 @@ SUBDIRS = test + CONFIG_CLEAN_FILES = *.loT *.rej *.orig + AM_CFLAGS = -fPIC -DPIC + PYLIBVER ?= python$(PYTHON_VERSION) +-AM_CPPFLAGS = -I. -I$(top_builddir) -I@PYINCLUDEDIR@ ++PYINC ?= /usr/include/$(PYLIBVER) ++AM_CPPFLAGS = -I. -I$(top_builddir) -I$(PYINC) + LIBS = $(top_builddir)/src/libcap-ng.la + SWIG_FLAGS = -python + SWIG_INCLUDES = ${AM_CPPFLAGS} +diff --git a/configure.ac b/configure.ac +index 1d777d5..9d90f64 100644 +--- a/configure.ac ++++ b/configure.ac +@@ -123,19 +123,8 @@ if test x$use_python = xno ; then + else + AC_MSG_RESULT(testing) + AM_PATH_PYTHON +-PYINCLUDEDIR=`python${am_cv_python_version} -c "from distutils importsysconfig; print(sysconfig.get_config_var('INCLUDEPY'))"`
+-if test -f ${PYINCLUDEDIR}/Python.h ; then +- python_found="yes" +- AC_SUBST(PYINCLUDEDIR) +- AC_MSG_NOTICE(Python bindings will be built) +-else +- python_found="no" +- if test x$use_python = xyes ; then +- AC_MSG_ERROR([Python explicitly required and python headers found]) +- else +- AC_MSG_WARN("Python headers not found - python bindings will not be made") +- fi +-fi++python_found="yes"
++AC_MSG_NOTICE(Python bindings will be built)
+ fi
+AM_CONDITIONAL(HAVE_PYTHON, test ${python_found} = "yes")meta/recipes-support/libcap-ng/libcap-ng/python.patch new file +4
-0+ +-- +1.8.4.2 +meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +3
-0@@ -0,0 +1,39 @@ +SUMMARY = "An alternate posix capabilities library" +DESCRIPTION = "The libcap-ng library is intended to make programming \ +with POSIX capabilities much easier than the traditional libcaplibrary."
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +4
-0+HOMEPAGE = "http://freecode.com/projects/libcap-ng" +SECTION = "base" +LICENSE = "GPLv2+ & LGPLv2.1+" +LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f\
+ file://COPYING.LIB;md5=e3eda01d9815f8d24aae2dbd89b68b06"meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +2
-0+ +SRC_URI ="http://people.redhat.com/sgrubb/libcap-ng/libcap-ng-${PV}.tar.gz \
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +6
-0+ file://python.patch" + +inherit lib_package autotools pythonnative + +SRC_URI[md5sum] = "3d7d126b29e2869a0257c17c8b0d9b2e" +SRC_URI[sha256sum] ="
615549ce39b333f6b78baee0c0b4ef18bc726c6bf1cca123dfd89dd963f6d06b"meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +6
-0+ +DEPENDS += "swig-native python" + +EXTRA_OECONF += "--without-python3" + +EXTRA_OEMAKE += "PYLIBVER='python${PYTHON_BASEVERSION}'PYINC='${STAGING_INCDIR}/${PYLIBVER}'"
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +14
-0+ +PACKAGES += "${PN}-python" + +FILES_${PN}-dbg += "${libdir}/python${PYTHON_BASEVERSION}/*/.debug" +FILES_${PN}-python = "${libdir}/python${PYTHON_BASEVERSION}" + +BBCLASSEXTEND = "native" + +do_install_append() { + # Moving libcap-ng to base_libdir + if [ ! ${D}${libdir} -ef ${D}${base_libdir} ]; then + mkdir -p ${D}/${base_libdir}/ + mv -f ${D}${libdir}/libcap-ng.so.* ${D}${base_libdir}/ + relpath=${@os.path.relpath("${base_libdir}","${libdir}")}
+ ln -sf ${relpath}/libcap-ng.so.0.0.0
${D}${libdir}/libcap-ng.someta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +2
-1+ fi +} --1.9.1
Quoted 5 lines
Quoted 5 lines
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON, Canada, K2K 2W5--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [PATCH 2/2 v2] libcap-ng: add package 0.7.7
Quoted 36 lines · Andre McCurdy
Quoted 29 lines · Randy MacLeod
Quoted 18 lines · Khem Raj
Quoted 16 lines · On Thu, Aug 20, 2015 at 10:38 PM, <[email protected]> wrote:
From: Wenzong Fan <[email protected]>
Pull package from meta-oe to oe-core:
meta-oe commit:bce4dba5546480c8e43c6442959ac7d0a4ef32f6The libcap-ng library is intended to make programming with posix capabilities much easier than the traditional libcap library.
It's not a replacement to libcap, it provides different library (libcap-ng.so) while packages explicitly look for libcap.so. It could be used by qemu, util-linux, libvirt, audit ...
With adding it to oe-core, the copies from following layers could be removed:
Quoted 8 lines
Quoted 1 line
* meta-oe, meta-selinux, meta-security-framework ...
I am afraid that we are setting a pretext for moving all recipes that are in multiple layers to be eligible for OE-core now. meta-oe is common layer for extended recipes, so may be other layers should have been a bit more vigilant and made sure
there requirements were met with whats in meta-oe.Quoted 4 lines
Meta-oe has far to many recipes for some people to want to include the entire layer:
meta-oe.git $ find meta-oe/ -name "*bb" | wc -l 618
Quoted 5 lines
I typically include most of the meta-oe layers, but I've never really given much thought to how many recipes there are.
Is the concern that parsing too many recipes makes bitbake slow? Or is there another reason why I wouldn't want to include them all?
Slow has nothing to do with it. It's purely from a support perspective. If we claim to our customers to support a layer, and don't make it explicit that certain pieces of it are 'unsupported', then we're on the hook for everything.
(I'm not singling out meta-oe BTW...) What we want is an easy way for our customers to use meta-oe, but also understand where our product support ends and custom or community support begins.
This whitelisting, subsetting, masking, blacklisting, etc are all ways we can accomplish this goal. I don't believe this is unique to my environment, but it's likely more common for OSVs then end device makers.
--Mark
Quoted 202 lines
Quoted 202 lines
We can certainly use the new whitelist layer filtering to get to a smaller collection of recipes but I'd like to suggest we need to document and maybe design the layer structure
a bit more. There are lots of different opinions about how to split collections of packages in to different layers so unless someone has a dependency-based analysis of all pacakges in all layers, I don't see much point in a long discussion on this topic.Has the idea of creating a new meta-openembedded layer for widely-used, OS interface libraries been proposed? These 80 recipes could be considered for inclusion:
$ find meta-oe -name "lib*bb" | wc -l 80 but more consideration is probably needed.In the short term (oe-core-1.9 (now 2.0), I guess we leave things as they are. Sigh...
../Randy
While I'm at it, for reference of layer size:
$ for i in `ls -d meta-*`; do echo -n $i": "; find $i -name "*bb" | wc -l; done meta-efl: 57 meta-filesystems: 16 meta-gnome: 82 meta-gpe: 5 meta-initramfs: 14 meta-multimedia: 51 meta-networking: 115 meta-oe: 618 meta-perl: 30 meta-python: 74 meta-ruby: 4 meta-systemd: 1 meta-webserver: 13 meta-xfce: 67-----------------------------------------
Quoted 139 lines
we should ask what core feature does it enable for reference images and machines.
Quoted 136 lines
Signed-off-by Wenzong Fan <[email protected]>--- .../libcap-ng/libcap-ng/python.patch | 58 ++++++++++++++++++++++ meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb | 39 +++++++++++++++ 2 files changed, 97 insertions(+)create mode 100644
meta/recipes-support/libcap-ng/libcap-ng/python.patch
create mode 100644 meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bbmeta/recipes-support/libcap-ng/libcap-ng/python.patch new file +38
-0@@ -0,0 +1,58 @@ +From b01bb2694f66cd981e6d61523433dc3eb5ed32f2 Mon Sep 17 00:00:00 2001 +From: Li xin <[email protected]> +Date: Sat, 18 Jul 2015 23:03:30 +0900 +Subject: [PATCH] configure.ac - Avoid an incorrect check for python. + Makefile.am - avoid hard coded host include paths. + +Upstream-Status: pending + +Signed-off-by: Mark Hatle <[email protected]> +Signed-off-by: Li Xin <[email protected]> +--- + bindings/python/Makefile.am | 3 ++- + configure.ac | 15 ++------------- + 2 files changed, 4 insertions(+), 14 deletions(-) + +diff --git a/bindings/python/Makefile.am b/bindings/python/Makefile.am +index 82b9bb8..f9fe7a8 100644 +--- a/bindings/python/Makefile.am ++++ b/bindings/python/Makefile.am +@@ -23,7 +23,8 @@ SUBDIRS = test + CONFIG_CLEAN_FILES = *.loT *.rej *.orig + AM_CFLAGS = -fPIC -DPIC + PYLIBVER ?= python$(PYTHON_VERSION) +-AM_CPPFLAGS = -I. -I$(top_builddir) -I@PYINCLUDEDIR@ ++PYINC ?= /usr/include/$(PYLIBVER) ++AM_CPPFLAGS = -I. -I$(top_builddir) -I$(PYINC) + LIBS = $(top_builddir)/src/libcap-ng.la + SWIG_FLAGS = -python + SWIG_INCLUDES = ${AM_CPPFLAGS} +diff --git a/configure.ac b/configure.ac +index 1d777d5..9d90f64 100644 +--- a/configure.ac ++++ b/configure.ac +@@ -123,19 +123,8 @@ if test x$use_python = xno ; then + else + AC_MSG_RESULT(testing) + AM_PATH_PYTHON +-PYINCLUDEDIR=`python${am_cv_python_version} -c "from distutils importsysconfig; print(sysconfig.get_config_var('INCLUDEPY'))"`
+-if test -f ${PYINCLUDEDIR}/Python.h ; then +- python_found="yes" +- AC_SUBST(PYINCLUDEDIR) +- AC_MSG_NOTICE(Python bindings will be built) +-else +- python_found="no" +- if test x$use_python = xyes ; then +- AC_MSG_ERROR([Python explicitly required and python headers found]) +- else +- AC_MSG_WARN("Python headers not found - python bindings will not be made") +- fi +-fi++python_found="yes"
++AC_MSG_NOTICE(Python bindings will be built)
+ fi
+AM_CONDITIONAL(HAVE_PYTHON, test ${python_found} = "yes")meta/recipes-support/libcap-ng/libcap-ng/python.patch new file +4
-0+ +-- +1.8.4.2 +meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +3
-0@@ -0,0 +1,39 @@ +SUMMARY = "An alternate posix capabilities library" +DESCRIPTION = "The libcap-ng library is intended to make programming \ +with POSIX capabilities much easier than the traditional libcaplibrary."
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +4
-0+HOMEPAGE = "http://freecode.com/projects/libcap-ng" +SECTION = "base" +LICENSE = "GPLv2+ & LGPLv2.1+" +LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f\
+ file://COPYING.LIB;md5=e3eda01d9815f8d24aae2dbd89b68b06"meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +2
-0+ +SRC_URI ="http://people.redhat.com/sgrubb/libcap-ng/libcap-ng-${PV}.tar.gz \
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +6
-0+ file://python.patch" + +inherit lib_package autotools pythonnative + +SRC_URI[md5sum] = "3d7d126b29e2869a0257c17c8b0d9b2e" +SRC_URI[sha256sum] ="
615549ce39b333f6b78baee0c0b4ef18bc726c6bf1cca123dfd89dd963f6d06b"meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +6
-0+ +DEPENDS += "swig-native python" + +EXTRA_OECONF += "--without-python3" + +EXTRA_OEMAKE += "PYLIBVER='python${PYTHON_BASEVERSION}'PYINC='${STAGING_INCDIR}/${PYLIBVER}'"
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +14
-0+ +PACKAGES += "${PN}-python" + +FILES_${PN}-dbg += "${libdir}/python${PYTHON_BASEVERSION}/*/.debug" +FILES_${PN}-python = "${libdir}/python${PYTHON_BASEVERSION}" + +BBCLASSEXTEND = "native" + +do_install_append() { + # Moving libcap-ng to base_libdir + if [ ! ${D}${libdir} -ef ${D}${base_libdir} ]; then + mkdir -p ${D}/${base_libdir}/ + mv -f ${D}${libdir}/libcap-ng.so.* ${D}${base_libdir}/ + relpath=${@os.path.relpath("${base_libdir}","${libdir}")}
+ ln -sf ${relpath}/libcap-ng.so.0.0.0
${D}${libdir}/libcap-ng.someta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +2
-1+ fi +} --1.9.1
Quoted 5 lines
Quoted 5 lines
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON, Canada, K2K 2W5--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [PATCH 2/2 v2] libcap-ng: add package 0.7.7
In reply to Andre McCurdyOn 2015-08-21 09:14 PM, Andre McCurdy wrote:> On Fri, Aug 21, 2015 at 5:55 PM, Randy MacLeod
Quoted 35 lines
Quoted 29 lines · <[email protected]> wrote:
Quoted 18 lines · Khem Raj
Quoted 16 lines · On Thu, Aug 20, 2015 at 10:38 PM, <[email protected]> wrote:
From: Wenzong Fan <[email protected]>
Pull package from meta-oe to oe-core:
meta-oe commit:bce4dba5546480c8e43c6442959ac7d0a4ef32f6The libcap-ng library is intended to make programming with posix capabilities much easier than the traditional libcap library.
It's not a replacement to libcap, it provides different library (libcap-ng.so) while packages explicitly look for libcap.so. It could be used by qemu, util-linux, libvirt, audit ...
With adding it to oe-core, the copies from following layers could be removed:
Quoted 8 lines
Quoted 1 line
* meta-oe, meta-selinux, meta-security-framework ...
I am afraid that we are setting a pretext for moving all recipes that are in multiple layers to be eligible for OE-core now. meta-oe is common layer for extended recipes, so may be other layers should have been a bit more vigilant and made sure
there requirements were met with whats in meta-oe.Quoted 4 lines
Meta-oe has far to many recipes for some people to want to include the entire layer:
meta-oe.git $ find meta-oe/ -name "*bb" | wc -l 618
Quoted 4 lines
I typically include most of the meta-oe layers, but I've never really given much thought to how many recipes there are.
Is the concern that parsing too many recipes makes bitbake slow? Or is
Parsing time and probably memory used scale ~ linearly with the number of recipes, so that's a *bit* of a concern especially since it's
Quoted 1 line
500 additional recipes or an increase of > 25% for our distro
but it's not the top issue.
Quoted 1 line
there another reason why I wouldn't want to include them all?
As Mark said, it's a business decision.
There are (probably more than linear) engineering costs to adding a recipe to a distribution. That's why we were using the meta-FOO-subset approach.
Of course, personally I'd like to provide the full set of meta-openembedded layers and more! We might be able to support all of meta-openembedded at some point but I don't think it's the right decision now.
../Randy
Quoted 20 lines
Quoted 20 lines
We can certainly use the new whitelist layer filtering to get to a smaller collection of recipes but I'd like to suggest we need to document and maybe design the layer structure
a bit more. There are lots of different opinions about how to split collections of packages in to different layers so unless someone has a dependency-based analysis of all pacakges in all layers, I don't see much point in a long discussion on this topic.Has the idea of creating a new meta-openembedded layer for widely-used, OS interface libraries been proposed? These 80 recipes could be considered for inclusion:
$ find meta-oe -name "lib*bb" | wc -l 80 but more consideration is probably needed.In the short term (oe-core-1.9 (now 2.0), I guess we leave things as they are. Sigh...
Quoted 6 lines
Quoted 6 lines
../Randy
While I'm at it, for reference of layer size:
$ for i in `ls -d meta-*`; do echo -n $i": "; find $i -name "*bb" |
wc -l;
Quoted 24 lines
Quoted 24 lines
done
meta-efl: 57
meta-filesystems: 16
meta-gnome: 82
meta-gpe: 5
meta-initramfs: 14
meta-multimedia: 51
meta-networking: 115
meta-oe: 618
meta-perl: 30
meta-python: 74
meta-ruby: 4
meta-systemd: 1
meta-webserver: 13
meta-xfce: 67-----------------------------------------
Quoted 4 lines
we should ask what core feature does it enable for reference images and machines.
Quoted 1 line
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Signed-off-by Wenzong Fan <[email protected]>--- .../libcap-ng/libcap-ng/python.patch | 58 ++++++++++++++++++++++ meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb | 39
+++++++++++++++
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
2 files changed, 97 insertions(+)create mode 100644
meta/recipes-support/libcap-ng/libcap-ng/python.patch
create mode 100644
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
meta/recipes-support/libcap-ng/libcap-ng/python.patch line 1
Quoted 9 lines
meta/recipes-support/libcap-ng/libcap-ng/python.patch new file +1
-0@@ -0,0 +1,58 @@ +From b01bb2694f66cd981e6d61523433dc3eb5ed32f2 Mon Sep 17
00:00:00 2001
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
meta/recipes-support/libcap-ng/libcap-ng/python.patch new file +7
-0+From: Li xin <[email protected]> +Date: Sat, 18 Jul 2015 23:03:30 +0900 +Subject: [PATCH] configure.ac - Avoid an incorrect check for python. + Makefile.am - avoid hard coded host include paths. + +Upstream-Status: pending +
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
meta/recipes-support/libcap-ng/libcap-ng/python.patch
Quoted 8 lines
meta/recipes-support/libcap-ng/libcap-ng/python.patch new file +8
-0+Signed-off-by: Mark Hatle <[email protected]> +Signed-off-by: Li Xin <[email protected]> +--- + bindings/python/Makefile.am | 3 ++- + configure.ac | 15 ++------------- + 2 files changed, 4 insertions(+), 14 deletions(-) + +diff --git a/bindings/python/Makefile.am
b/bindings/python/Makefile.am
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
meta/recipes-support/libcap-ng/libcap-ng/python.patch new file +14
-0+index 82b9bb8..f9fe7a8 100644 +--- a/bindings/python/Makefile.am ++++ b/bindings/python/Makefile.am +@@ -23,7 +23,8 @@ SUBDIRS = test + CONFIG_CLEAN_FILES = *.loT *.rej *.orig + AM_CFLAGS = -fPIC -DPIC + PYLIBVER ?= python$(PYTHON_VERSION) +-AM_CPPFLAGS = -I. -I$(top_builddir) -I@PYINCLUDEDIR@ ++PYINC ?= /usr/include/$(PYLIBVER) ++AM_CPPFLAGS = -I. -I$(top_builddir) -I$(PYINC) + LIBS = $(top_builddir)/src/libcap-ng.la + SWIG_FLAGS = -python + SWIG_INCLUDES = ${AM_CPPFLAGS} +diff --git a/configure.ac b/configure.ac
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
meta/recipes-support/libcap-ng/libcap-ng/python.patch
Quoted 8 lines
meta/recipes-support/libcap-ng/libcap-ng/python.patch new file +8
-0+index 1d777d5..9d90f64 100644 +--- a/configure.ac ++++ b/configure.ac +@@ -123,19 +123,8 @@ if test x$use_python = xno ; then + else + AC_MSG_RESULT(testing) + AM_PATH_PYTHON +-PYINCLUDEDIR=`python${am_cv_python_version} -c "from distutils
import
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
sysconfig; print(sysconfig.get_config_var('INCLUDEPY'))"`
+-if test -f ${PYINCLUDEDIR}/Python.h ; then +- python_found="yes" +- AC_SUBST(PYINCLUDEDIR)
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
+- AC_MSG_NOTICE(Python bindings will be built) +-else +- python_found="no" +- if test x$use_python = xyes ; then +- AC_MSG_ERROR([Python explicitly required and python headers found]) +- else +- AC_MSG_WARN("Python headers not found - python
bindings
Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
will not be made")
+- fi +-fi++python_found="yes"
++AC_MSG_NOTICE(Python bindings will be built)
+ fi
+AM_CONDITIONAL(HAVE_PYTHON, test ${python_found} = "yes")meta/recipes-support/libcap-ng/libcap-ng/python.patch new file +4
-0+ +-- +1.8.4.2 +(quoted diff) +0
-0
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb line 2
Quoted 8 lines
b/meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file mode 100644
index 0000000..a31d5dcmeta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +2
-0@@ -0,0 +1,39 @@ +SUMMARY = "An alternate posix capabilities library" +DESCRIPTION = "The libcap-ng library is intended to make
programming \
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb
Quoted 6 lines
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +1
-0+with POSIX capabilities much easier than the traditional libcaplibrary."
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +4
-0+HOMEPAGE = "http://freecode.com/projects/libcap-ng" +SECTION = "base" +LICENSE = "GPLv2+ & LGPLv2.1+" +LIC_FILES_CHKSUM =
"file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f
Quoted 25 lines
Quoted 25 lines
Quoted 25 lines
Quoted 25 lines
\
+ file://COPYING.LIB;md5=e3eda01d9815f8d24aae2dbd89b68b06"meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +2
-0+ +SRC_URI ="http://people.redhat.com/sgrubb/libcap-ng/libcap-ng-${PV}.tar.gz \
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +6
-0+ file://python.patch" + +inherit lib_package autotools pythonnative + +SRC_URI[md5sum] = "3d7d126b29e2869a0257c17c8b0d9b2e" +SRC_URI[sha256sum] ="
615549ce39b333f6b78baee0c0b4ef18bc726c6bf1cca123dfd89dd963f6d06b"meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +6
-0+ +DEPENDS += "swig-native python" + +EXTRA_OECONF += "--without-python3" + +EXTRA_OEMAKE += "PYLIBVER='python${PYTHON_BASEVERSION}'PYINC='${STAGING_INCDIR}/${PYLIBVER}'"
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +5
-0+ +PACKAGES += "${PN}-python" + +FILES_${PN}-dbg += "${libdir}/python${PYTHON_BASEVERSION}/*/.debug" +FILES_${PN}-python = "${libdir}/python${PYTHON_BASEVERSION}"
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb
Quoted 8 lines
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +8
-0+ +BBCLASSEXTEND = "native" + +do_install_append() { + # Moving libcap-ng to base_libdir + if [ ! ${D}${libdir} -ef ${D}${base_libdir} ]; then + mkdir -p ${D}/${base_libdir}/ + mv -f ${D}${libdir}/libcap-ng.so.*
${D}${base_libdir}/
Quoted 17 lines
Quoted 17 lines
Quoted 14 lines
Quoted 14 lines
+ relpath=${@os.path.relpath("${base_libdir}",
"${libdir}")}
+ ln -sf ${relpath}/libcap-ng.so.0.0.0
${D}${libdir}/libcap-ng.someta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +2
-1+ fi +} --1.9.1
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 3 lines
Quoted 3 lines
--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON,
Canada,
Quoted 7 lines
Quoted 7 lines
K2K 2W5
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Signature · 2 lines
# Randy MacLeod. SMTS, Linux, Wind River Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON, Canada, K2K 2W5
Quoted 29 lines · Randy MacLeod
Quoted 18 lines · Khem Raj
Quoted 16 lines · On Thu, Aug 20, 2015 at 10:38 PM, <[email protected]> wrote:
From: Wenzong Fan <[email protected]>
Pull package from meta-oe to oe-core:
meta-oe commit:bce4dba5546480c8e43c6442959ac7d0a4ef32f6The libcap-ng library is intended to make programming with posix capabilities much easier than the traditional libcap library.
It's not a replacement to libcap, it provides different library (libcap-ng.so) while packages explicitly look for libcap.so. It could be used by qemu, util-linux, libvirt, audit ...
With adding it to oe-core, the copies from following layers could be removed:
Quoted 8 lines
Quoted 1 line
* meta-oe, meta-selinux, meta-security-framework ...
I am afraid that we are setting a pretext for moving all recipes that are in multiple layers to be eligible for OE-core now. meta-oe is common layer for extended recipes, so may be other layers should have been a bit more vigilant and made sure
there requirements were met with whats in meta-oe.
Quoted 4 lines
Meta-oe has far to many recipes for some people to want to include the entire layer:
meta-oe.git $ find meta-oe/ -name "*bb" | wc -l 618
I typically include most of the meta-oe layers, but I've never really given much thought to how many recipes there are.
Is the concern that parsing too many recipes makes bitbake slow? Or is there another reason why I wouldn't want to include them all?
Quoted 202 lines
We can certainly use the new whitelist layer filtering to get to a smaller collection of recipes but I'd like to suggest we need to document and maybe design the layer structure
a bit more. There are lots of different opinions about how to split collections of packages in to different layers so unless someone has a dependency-based analysis of all pacakges in all layers, I don't see much point in a long discussion on this topic.Has the idea of creating a new meta-openembedded layer for widely-used, OS interface libraries been proposed? These 80 recipes could be considered for inclusion:
$ find meta-oe -name "lib*bb" | wc -l 80 but more consideration is probably needed.In the short term (oe-core-1.9 (now 2.0), I guess we leave things as they are. Sigh...
../Randy
While I'm at it, for reference of layer size:
$ for i in `ls -d meta-*`; do echo -n $i": "; find $i -name "*bb" | wc -l; done meta-efl: 57 meta-filesystems: 16 meta-gnome: 82 meta-gpe: 5 meta-initramfs: 14 meta-multimedia: 51 meta-networking: 115 meta-oe: 618 meta-perl: 30 meta-python: 74 meta-ruby: 4 meta-systemd: 1 meta-webserver: 13 meta-xfce: 67-----------------------------------------
Quoted 139 lines
we should ask what core feature does it enable for reference images and machines.
Quoted 136 lines
Signed-off-by Wenzong Fan <[email protected]>--- .../libcap-ng/libcap-ng/python.patch | 58 ++++++++++++++++++++++ meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb | 39 +++++++++++++++ 2 files changed, 97 insertions(+)create mode 100644
meta/recipes-support/libcap-ng/libcap-ng/python.patch
create mode 100644 meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bbmeta/recipes-support/libcap-ng/libcap-ng/python.patch new file +38
-0@@ -0,0 +1,58 @@ +From b01bb2694f66cd981e6d61523433dc3eb5ed32f2 Mon Sep 17 00:00:00 2001 +From: Li xin <[email protected]> +Date: Sat, 18 Jul 2015 23:03:30 +0900 +Subject: [PATCH] configure.ac - Avoid an incorrect check for python. + Makefile.am - avoid hard coded host include paths. + +Upstream-Status: pending + +Signed-off-by: Mark Hatle <[email protected]> +Signed-off-by: Li Xin <[email protected]> +--- + bindings/python/Makefile.am | 3 ++- + configure.ac | 15 ++------------- + 2 files changed, 4 insertions(+), 14 deletions(-) + +diff --git a/bindings/python/Makefile.am b/bindings/python/Makefile.am +index 82b9bb8..f9fe7a8 100644 +--- a/bindings/python/Makefile.am ++++ b/bindings/python/Makefile.am +@@ -23,7 +23,8 @@ SUBDIRS = test + CONFIG_CLEAN_FILES = *.loT *.rej *.orig + AM_CFLAGS = -fPIC -DPIC + PYLIBVER ?= python$(PYTHON_VERSION) +-AM_CPPFLAGS = -I. -I$(top_builddir) -I@PYINCLUDEDIR@ ++PYINC ?= /usr/include/$(PYLIBVER) ++AM_CPPFLAGS = -I. -I$(top_builddir) -I$(PYINC) + LIBS = $(top_builddir)/src/libcap-ng.la + SWIG_FLAGS = -python + SWIG_INCLUDES = ${AM_CPPFLAGS} +diff --git a/configure.ac b/configure.ac +index 1d777d5..9d90f64 100644 +--- a/configure.ac ++++ b/configure.ac +@@ -123,19 +123,8 @@ if test x$use_python = xno ; then + else + AC_MSG_RESULT(testing) + AM_PATH_PYTHON +-PYINCLUDEDIR=`python${am_cv_python_version} -c "from distutils importsysconfig; print(sysconfig.get_config_var('INCLUDEPY'))"`
+-if test -f ${PYINCLUDEDIR}/Python.h ; then +- python_found="yes" +- AC_SUBST(PYINCLUDEDIR) +- AC_MSG_NOTICE(Python bindings will be built) +-else +- python_found="no" +- if test x$use_python = xyes ; then +- AC_MSG_ERROR([Python explicitly required and python headers found]) +- else +- AC_MSG_WARN("Python headers not found - python bindings will not be made") +- fi +-fi++python_found="yes"
++AC_MSG_NOTICE(Python bindings will be built)
+ fi
+AM_CONDITIONAL(HAVE_PYTHON, test ${python_found} = "yes")meta/recipes-support/libcap-ng/libcap-ng/python.patch new file +4
-0+ +-- +1.8.4.2 +meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +3
-0@@ -0,0 +1,39 @@ +SUMMARY = "An alternate posix capabilities library" +DESCRIPTION = "The libcap-ng library is intended to make programming \ +with POSIX capabilities much easier than the traditional libcaplibrary."
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +4
-0+HOMEPAGE = "http://freecode.com/projects/libcap-ng" +SECTION = "base" +LICENSE = "GPLv2+ & LGPLv2.1+" +LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f\
+ file://COPYING.LIB;md5=e3eda01d9815f8d24aae2dbd89b68b06"meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +2
-0+ +SRC_URI ="http://people.redhat.com/sgrubb/libcap-ng/libcap-ng-${PV}.tar.gz \
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +6
-0+ file://python.patch" + +inherit lib_package autotools pythonnative + +SRC_URI[md5sum] = "3d7d126b29e2869a0257c17c8b0d9b2e" +SRC_URI[sha256sum] ="
615549ce39b333f6b78baee0c0b4ef18bc726c6bf1cca123dfd89dd963f6d06b"meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +6
-0+ +DEPENDS += "swig-native python" + +EXTRA_OECONF += "--without-python3" + +EXTRA_OEMAKE += "PYLIBVER='python${PYTHON_BASEVERSION}'PYINC='${STAGING_INCDIR}/${PYLIBVER}'"
meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +14
-0+ +PACKAGES += "${PN}-python" + +FILES_${PN}-dbg += "${libdir}/python${PYTHON_BASEVERSION}/*/.debug" +FILES_${PN}-python = "${libdir}/python${PYTHON_BASEVERSION}" + +BBCLASSEXTEND = "native" + +do_install_append() { + # Moving libcap-ng to base_libdir + if [ ! ${D}${libdir} -ef ${D}${base_libdir} ]; then + mkdir -p ${D}/${base_libdir}/ + mv -f ${D}${libdir}/libcap-ng.so.* ${D}${base_libdir}/ + relpath=${@os.path.relpath("${base_libdir}","${libdir}")}
+ ln -sf ${relpath}/libcap-ng.so.0.0.0
${D}${libdir}/libcap-ng.someta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +2
-1+ fi +} --1.9.1
Quoted 5 lines
Quoted 5 lines
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON, Canada, K2K 2W5--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [PATCH 2/2 v2] libcap-ng: add package 0.7.7
Quoted 9 lines · Randy MacLeod
Parsing time and probably memory used scale ~ linearly with the number of recipes, so that's a *bit* of a concern especially since it's
Quoted 1 line
500 additional recipes or an increase of > 25% for our distro
but it's not the top issue.
Quoted 1 line
there another reason why I wouldn't want to include them all?
As Mark said, it's a business decision.
Quoted 8 lines
There are (probably more than linear) engineering costs to adding a recipe to a distribution. That's why we were using the meta-FOO-subset approach.
Of course, personally I'd like to provide the full set of meta-openembedded layers and more! We might be able to support all of meta-openembedded at some point but I don't think it's the right decision now.
Its fine, and you are free to do whatever you wish to in your fork. Its when these policies start to shape up layers, that's when we have to be vigilant
and thats the point I have been raising.
Re: [PATCH 2/2 v2] libcap-ng: add package 0.7.7
In reply to Randy MacLeodQuoted 28 lines · Randy MacLeod
Quoted 16 lines · Khem Raj
Quoted 15 lines · On Thu, Aug 20, 2015 at 10:38 PM, <[email protected]> wrote:
From: Wenzong Fan <[email protected]>
Pull package from meta-oe to oe-core:
meta-oe commit:bce4dba5546480c8e43c6442959ac7d0a4ef32f6The libcap-ng library is intended to make programming with posix capabilities much easier than the traditional libcap library.
It's not a replacement to libcap, it provides different library (libcap-ng.so) while packages explicitly look for libcap.so. It could be used by qemu, util-linux, libvirt, audit ...
With adding it to oe-core, the copies from following layers could be removed:
Quoted 7 lines
Quoted 1 line
* meta-oe, meta-selinux, meta-security-framework ...
I am afraid that we are setting a pretext for moving all recipes that are in multiple layers to be eligible for OE-core now. meta-oe is common layer for extended recipes, so may be other layers should have been a bit more vigilant and made sure
there requirements were met with whats in meta-oe.
Quoted 12 lines
Meta-oe has far to many recipes for some people to want to include the entire layer:
meta-oe.git $ find meta-oe/ -name "*bb" | wc -l
618
We can certainly use the new whitelist layer filtering to get to a smaller collection of recipes but I'd like to suggest we need to document and maybe design the layer structure
a bit more. There are lots of different opinions about how to split collections of packages in to different layers so unless someone has a dependency-based analysis of all pacakges in all layers, I don't see much point in a long discussion on this topic.
if someone wants to ignore certain recipes use BBMASK, I do not think this whitelisting is a good idea, it does not help in maintaining layer quality, and its much better that we maintained layers in good quality collectively may be with some extra recipes in it instead of cannibalizing few recipes from it into private layers or other layer which one happens to use. It seriously dents the layers user base and quality. If meta-oe hosts certain layers that could be a fit in another middleware or topic layer, lets move it to that layer but lets not encourage the behavior of duplicating the recipes or severely crippling the layer before using it.
Quoted 10 lines
Has the idea of creating a new meta-openembedded layer for widely-used, OS interface libraries been proposed? These 80 recipes could be considered for inclusion:
$ find meta-oe -name "lib*bb" | wc -l 80 but more consideration is probably needed.In the short term (oe-core-1.9 (now 2.0), I guess we leave things as they are. Sigh…
number of layers is a delicate balance too. The more you divide them more smaller the userbase will become and complex becomes the distros.
Quoted 159 lines
../Randy
While I'm at it, for reference of layer size:
$ for i in `ls -d meta-*`; do echo -n $i": "; find $i -name "*bb" | wc -l; done meta-efl: 57 meta-filesystems: 16 meta-gnome: 82 meta-gpe: 5 meta-initramfs: 14 meta-multimedia: 51 meta-networking: 115 meta-oe: 618 meta-perl: 30 meta-python: 74 meta-ruby: 4 meta-systemd: 1 meta-webserver: 13 meta-xfce: 67-----------------------------------------
Quoted 124 lines
we should ask what core feature does it enable for reference images and machines.
Quoted 121 lines
Signed-off-by Wenzong Fan <[email protected]>--- .../libcap-ng/libcap-ng/python.patch | 58 ++++++++++++++++++++++ meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb | 39 +++++++++++++++ 2 files changed, 97 insertions(+) create mode 100644 meta/recipes-support/libcap-ng/libcap-ng/python.patch create mode 100644 meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bbmeta/recipes-support/libcap-ng/libcap-ng/python.patch new file +58
-0@@ -0,0 +1,58 @@ +From b01bb2694f66cd981e6d61523433dc3eb5ed32f2 Mon Sep 17 00:00:00 2001 +From: Li xin <[email protected]> +Date: Sat, 18 Jul 2015 23:03:30 +0900 +Subject: [PATCH] configure.ac - Avoid an incorrect check for python. + Makefile.am - avoid hard coded host include paths. + +Upstream-Status: pending + +Signed-off-by: Mark Hatle <[email protected]> +Signed-off-by: Li Xin <[email protected]> +--- + bindings/python/Makefile.am | 3 ++- + configure.ac | 15 ++------------- + 2 files changed, 4 insertions(+), 14 deletions(-) + +diff --git a/bindings/python/Makefile.am b/bindings/python/Makefile.am +index 82b9bb8..f9fe7a8 100644 +--- a/bindings/python/Makefile.am ++++ b/bindings/python/Makefile.am +@@ -23,7 +23,8 @@ SUBDIRS = test + CONFIG_CLEAN_FILES = *.loT *.rej *.orig + AM_CFLAGS = -fPIC -DPIC + PYLIBVER ?= python$(PYTHON_VERSION) +-AM_CPPFLAGS = -I. -I$(top_builddir) -I@PYINCLUDEDIR@ ++PYINC ?= /usr/include/$(PYLIBVER) ++AM_CPPFLAGS = -I. -I$(top_builddir) -I$(PYINC) + LIBS = $(top_builddir)/src/libcap-ng.la + SWIG_FLAGS = -python + SWIG_INCLUDES = ${AM_CPPFLAGS} +diff --git a/configure.ac b/configure.ac +index 1d777d5..9d90f64 100644 +--- a/configure.ac ++++ b/configure.ac +@@ -123,19 +123,8 @@ if test x$use_python = xno ; then + else + AC_MSG_RESULT(testing) + AM_PATH_PYTHON +-PYINCLUDEDIR=`python${am_cv_python_version} -c "from distutils import sysconfig; print(sysconfig.get_config_var('INCLUDEPY'))"` +-if test -f ${PYINCLUDEDIR}/Python.h ; then +- python_found="yes" +- AC_SUBST(PYINCLUDEDIR) +- AC_MSG_NOTICE(Python bindings will be built) +-else +- python_found="no" +- if test x$use_python = xyes ; then +- AC_MSG_ERROR([Python explicitly required and python headers found]) +- else +- AC_MSG_WARN("Python headers not found - python bindings will not be made") +- fi +-fi ++python_found="yes" ++AC_MSG_NOTICE(Python bindings will be built) + fi + AM_CONDITIONAL(HAVE_PYTHON, test ${python_found} = "yes") + +-- +1.8.4.2 +meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +39
-1@@ -0,0 +1,39 @@ +SUMMARY = "An alternate posix capabilities library" +DESCRIPTION = "The libcap-ng library is intended to make programming \ +with POSIX capabilities much easier than the traditional libcap library." +HOMEPAGE = "http://freecode.com/projects/libcap-ng" +SECTION = "base" +LICENSE = "GPLv2+ & LGPLv2.1+" +LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \ + file://COPYING.LIB;md5=e3eda01d9815f8d24aae2dbd89b68b06" + +SRC_URI = "http://people.redhat.com/sgrubb/libcap-ng/libcap-ng-${PV}.tar.gz \ + file://python.patch" + +inherit lib_package autotools pythonnative + +SRC_URI[md5sum] = "3d7d126b29e2869a0257c17c8b0d9b2e" +SRC_URI[sha256sum] = "615549ce39b333f6b78baee0c0b4ef18bc726c6bf1cca123dfd89dd963f6d06b" + +DEPENDS += "swig-native python" + +EXTRA_OECONF += "--without-python3" + +EXTRA_OEMAKE += "PYLIBVER='python${PYTHON_BASEVERSION}' PYINC='${STAGING_INCDIR}/${PYLIBVER}'" + +PACKAGES += "${PN}-python" + +FILES_${PN}-dbg += "${libdir}/python${PYTHON_BASEVERSION}/*/.debug" +FILES_${PN}-python = "${libdir}/python${PYTHON_BASEVERSION}" + +BBCLASSEXTEND = "native" + +do_install_append() { + # Moving libcap-ng to base_libdir + if [ ! ${D}${libdir} -ef ${D}${base_libdir} ]; then + mkdir -p ${D}/${base_libdir}/ + mv -f ${D}${libdir}/libcap-ng.so.* ${D}${base_libdir}/ + relpath=${@os.path.relpath("${base_libdir}", "${libdir}")} + ln -sf ${relpath}/libcap-ng.so.0.0.0 ${D}${libdir}/libcap-ng.so + fi +} --1.9.1
Quoted 5 lines
Quoted 5 lines
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON, Canada, K2K 2W5
Re: [PATCH 2/2 v2] libcap-ng: add package 0.7.7
In reply to Khem RajQuoted 18 lines · Khem Raj
Quoted 8 lines · On Thu, Aug 20, 2015 at 10:38 PM, <[email protected]> wrote:
From: Wenzong Fan <[email protected]>
Pull package from meta-oe to oe-core:
meta-oe commit:bce4dba5546480c8e43c6442959ac7d0a4ef32f6The libcap-ng library is intended to make programming with posix capabilities much easier than the traditional libcap library.
Quoted 8 lines
It's not a replacement to libcap, it provides different library (libcap-ng.so) while packages explicitly look for libcap.so. It could be used by qemu, util-linux, libvirt, audit ...
With adding it to oe-core, the copies from following layers could be removed:
* meta-oe, meta-selinux, meta-security-framework ...
Quoted 7 lines
I am afraid that we are setting a pretext for moving all recipes that are in multiple layers to be eligible for OE-core now. met-oe is common layer for extended recipes, so may be other layers should have been a bit more vigilant and made sure
there requirements were met with whats in meta-oe.
we should ask what core feature does it enable for reference images and machines.
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.
--Mark
Quoted 126 lines
Quoted 126 lines
Signed-off-by Wenzong Fan <[email protected]>--- .../libcap-ng/libcap-ng/python.patch | 58 ++++++++++++++++++++++ meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb | 39 +++++++++++++++ 2 files changed, 97 insertions(+) create mode 100644 meta/recipes-support/libcap-ng/libcap-ng/python.patch create mode 100644 meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bbmeta/recipes-support/libcap-ng/libcap-ng/python.patch new file +58
-0@@ -0,0 +1,58 @@ +From b01bb2694f66cd981e6d61523433dc3eb5ed32f2 Mon Sep 17 00:00:00 2001 +From: Li xin <[email protected]> +Date: Sat, 18 Jul 2015 23:03:30 +0900 +Subject: [PATCH] configure.ac - Avoid an incorrect check for python. + Makefile.am - avoid hard coded host include paths. + +Upstream-Status: pending + +Signed-off-by: Mark Hatle <[email protected]> +Signed-off-by: Li Xin <[email protected]> +--- + bindings/python/Makefile.am | 3 ++- + configure.ac | 15 ++------------- + 2 files changed, 4 insertions(+), 14 deletions(-) + +diff --git a/bindings/python/Makefile.am b/bindings/python/Makefile.am +index 82b9bb8..f9fe7a8 100644 +--- a/bindings/python/Makefile.am ++++ b/bindings/python/Makefile.am +@@ -23,7 +23,8 @@ SUBDIRS = test + CONFIG_CLEAN_FILES = *.loT *.rej *.orig + AM_CFLAGS = -fPIC -DPIC + PYLIBVER ?= python$(PYTHON_VERSION) +-AM_CPPFLAGS = -I. -I$(top_builddir) -I@PYINCLUDEDIR@ ++PYINC ?= /usr/include/$(PYLIBVER) ++AM_CPPFLAGS = -I. -I$(top_builddir) -I$(PYINC) + LIBS = $(top_builddir)/src/libcap-ng.la + SWIG_FLAGS = -python + SWIG_INCLUDES = ${AM_CPPFLAGS} +diff --git a/configure.ac b/configure.ac +index 1d777d5..9d90f64 100644 +--- a/configure.ac ++++ b/configure.ac +@@ -123,19 +123,8 @@ if test x$use_python = xno ; then + else + AC_MSG_RESULT(testing) + AM_PATH_PYTHON +-PYINCLUDEDIR=`python${am_cv_python_version} -c "from distutils import sysconfig; print(sysconfig.get_config_var('INCLUDEPY'))"` +-if test -f ${PYINCLUDEDIR}/Python.h ; then +- python_found="yes" +- AC_SUBST(PYINCLUDEDIR) +- AC_MSG_NOTICE(Python bindings will be built) +-else +- python_found="no" +- if test x$use_python = xyes ; then +- AC_MSG_ERROR([Python explicitly required and python headers found]) +- else +- AC_MSG_WARN("Python headers not found - python bindings will not be made") +- fi +-fi ++python_found="yes" ++AC_MSG_NOTICE(Python bindings will be built) + fi + AM_CONDITIONAL(HAVE_PYTHON, test ${python_found} = "yes") + +-- +1.8.4.2 +meta/recipes-support/libcap-ng/libcap-ng_0.7.7.bb new file +39
-1@@ -0,0 +1,39 @@ +SUMMARY = "An alternate posix capabilities library" +DESCRIPTION = "The libcap-ng library is intended to make programming \ +with POSIX capabilities much easier than the traditional libcap library." +HOMEPAGE = "http://freecode.com/projects/libcap-ng" +SECTION = "base" +LICENSE = "GPLv2+ & LGPLv2.1+" +LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \ + file://COPYING.LIB;md5=e3eda01d9815f8d24aae2dbd89b68b06" + +SRC_URI = "http://people.redhat.com/sgrubb/libcap-ng/libcap-ng-${PV}.tar.gz \ + file://python.patch" + +inherit lib_package autotools pythonnative + +SRC_URI[md5sum] = "3d7d126b29e2869a0257c17c8b0d9b2e" +SRC_URI[sha256sum] = "615549ce39b333f6b78baee0c0b4ef18bc726c6bf1cca123dfd89dd963f6d06b" + +DEPENDS += "swig-native python" + +EXTRA_OECONF += "--without-python3" + +EXTRA_OEMAKE += "PYLIBVER='python${PYTHON_BASEVERSION}' PYINC='${STAGING_INCDIR}/${PYLIBVER}'" + +PACKAGES += "${PN}-python" + +FILES_${PN}-dbg += "${libdir}/python${PYTHON_BASEVERSION}/*/.debug" +FILES_${PN}-python = "${libdir}/python${PYTHON_BASEVERSION}" + +BBCLASSEXTEND = "native" + +do_install_append() { + # Moving libcap-ng to base_libdir + if [ ! ${D}${libdir} -ef ${D}${base_libdir} ]; then + mkdir -p ${D}/${base_libdir}/ + mv -f ${D}${libdir}/libcap-ng.so.* ${D}${base_libdir}/ + relpath=${@os.path.relpath("${base_libdir}", "${libdir}")} + ln -sf ${relpath}/libcap-ng.so.0.0.0 ${D}${libdir}/libcap-ng.so + fi +} --1.9.1
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [PATCH 2/2 v2] libcap-ng: add package 0.7.7
Quoted 6 lines · Mark Hatle
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.
Quoted 7 lines
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.
Re: [PATCH 2/2 v2] libcap-ng: add package 0.7.7
Quoted 15 lines · Khem Raj
Quoted 6 lines · Mark Hatle
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.
Quoted 7 lines
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.
Quoted 8 lines
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 handfullibcap-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
Quoted 25 lines
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
dbusThat 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.