Skip to contentSkip to conversation

libcap: drop obsolete attr PACKAGECONFIG option and libattr dependency

PATCH New Andre McCurdy 1 participant 1 message Apr 20, 2017

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 libcap: drop obsolete attr PACKAGECONFIG option and libattr dependency

In the 2.25 release, libcap dropped its dependency on an external libattr library:

https://git.kernel.org/pub/scm/linux/kernel/git/morgan/libcap.git/commit/?id=85f38a573fc47472ab792e813b6f6b6f0b1df112

---
 meta/recipes-support/libcap/libcap_2.25.bb | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)
meta/recipes-support/libcap/libcap_2.25.bb +1 -3
index 26d7bf2..0587e77 100644
@@ -27,11 +27,9 @@ do_configure() {
 	sed -e '/shell gperf/cifeq (,yes)' -i libcap/Makefile
 }
 
-PACKAGECONFIG ??= "${@bb.utils.filter('DISTRO_FEATURES', 'pam', d)} \
-                   ${@bb.utils.contains('DISTRO_FEATURES', 'xattr', 'attr', '', d)}"
+PACKAGECONFIG ??= "${@bb.utils.filter('DISTRO_FEATURES', 'pam', d)}"
 PACKAGECONFIG_class-native ??= ""
 
-PACKAGECONFIG[attr] = "LIBATTR=yes,LIBATTR=no,attr"
 PACKAGECONFIG[pam] = "PAM_CAP=yes,PAM_CAP=no,libpam"
 
 EXTRA_OEMAKE = " \
Signature · 1 line
1.9.1