Re: [PATCH 0/3] preserve xattrs in images

[Mark Hatle <mark.hatle@windriver.com>]

Is there something here that enables the tar-replacement-native?  Or is the user
just expected to know they need it?

If you look at meta/classes/sanity.bbclass, there is already a tar check for a
specific old version that can't handle overwriting symlinks properly.  It should
be possible to check for the distro feature of xattr and that the host tar has
this.  It would be good to prevent the user from having a problem early (sanity)
rather then at filesystem generation time.

--Mark

On 8/11/15 3:44 AM, Patrick Ohly wrote:
> Both Smack and IMA/EVM rely on xattrs in the rootfs. This works for
> .ext3/.ext4 images, but not for .jffs2 and .tar.bz2. These changes
> allow optionally building also such images with xattrs without
> changing the default (which still is to ignore xattrs in .jffs2 and
> .tar.bz2).
> 
> The default does not get changed because supporting xattrs causes a
> certain overhead (need to build GNU tar, additional system calls when
> creating the images).
> 
> See https://github.com/01org/meta-intel-iot-security/pull/34 for code using
> these changes.
> 
> The following changes since commit 5094354a2811825e6d60963f03959daa349cab23:
> 
>   bind: upgrade to 9.10.2-p3 (2015-08-09 15:14:32 -0700)
> 
> are available in the git repository at:
> 
>   git://github.com/pohly/openembedded-core xattr
>   https://github.com/pohly/openembedded-core/tree/xattr
> 
> Patrick Ohly (3):
>   tar-replacement-native: avoid race condition with host tar
>   image_types.bbclass: allow replacing tar command
>   mtd-utils: keep xattr support enabled
> 
>  meta/classes/image_types.bbclass                         | 13 ++++++++++++-
>  meta/recipes-devtools/mtd/mtd-utils_git.bb               |  2 +-
>  meta/recipes-extended/tar/tar-replacement-native_1.28.bb | 14 +++++++++++++-
>  3 files changed, 26 insertions(+), 3 deletions(-)
>