bitbake.conf: Add xattr to DISTRO_FEATURES_NATIVE

Commit db1f1adace58763c35774e3fdfeaac5c3ca646fd disabled 'xattr' from
DISTRO_FEATURES when native packages are built, whereas for target
packages it was retained. This changed eg. mtd-utils-native to build
without extended attributes (capabilities) support from there on.

Thus even setcap was called succesfully for a binary during pkg_postinst
on build host, the capabilities did not exist on target rootfs due to
now xattr-less host-side mkfs utility.

Adding xattr to DISTRO_FEATURES_NATIVE restores previous behaviour,
fixing the discontinuity in capability propagation to target
device rootfs.

(From OE-Core rev: 2ad3b8ae1c56a46bf14fc6bc4c34e4b3a568d741)

Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 1 insertions, 1 deletions

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 489a161e17..7007a6e9b6 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -808,7 +808,7 @@ IMAGE_FEATURES += "${EXTRA_IMAGE_FEATURES}"
 
 # Native distro features (will always be used for -native, even if they
 # are not enabled for target)
-DISTRO_FEATURES_NATIVE ?= "x11 ipv6"
+DISTRO_FEATURES_NATIVE ?= "x11 ipv6 xattr"
 DISTRO_FEATURES_NATIVESDK ?= "x11 libc-charsets libc-locales libc-locale-code"
 
 # Normally target distro features will not be applied to native builds: