diff options
| author | Niko Mauno <niko.mauno@vaisala.com> | 2018-01-31 18:55:10 +0200 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-02-06 10:54:33 +0000 |
| commit | 2ad3b8ae1c56a46bf14fc6bc4c34e4b3a568d741 (patch) | |
| tree | 9e0c5cee97c9d6d2b0fef9cb5a16ddc775f4cb77 /scripts/lib/devtool/utilcmds.py | |
| parent | a0988c3374e964170d1d24fc230306b887432d31 (diff) | |
| download | openembedded-core-2ad3b8ae1c56a46bf14fc6bc4c34e4b3a568d741.tar.gz openembedded-core-2ad3b8ae1c56a46bf14fc6bc4c34e4b3a568d741.tar.bz2 openembedded-core-2ad3b8ae1c56a46bf14fc6bc4c34e4b3a568d741.zip | |
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.
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'scripts/lib/devtool/utilcmds.py')
0 files changed, 0 insertions, 0 deletions