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
On Wed, 2015-08-12 at 09:34 -0500, Mark Hatle wrote:
Is there something here that enables the tar-replacement-native? Or is the
user
just expected to know they need it?
The user is supposed to ensure that it gets depended on if (and only if)
needed.
I gave the following usage instructions
On Tue, 2015-08-11 at 15:29 +0100, Burton, Ross wrote:
Hi Patrick,
On 11 August 2015 at 09:44, Patrick Ohly patrick.o...@intel.com
wrote:
The default does not get changed because supporting xattrs
causes a
certain overhead (need to build GNU tar, additional system
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
Hi Patrick,
On 11 August 2015 at 09:44, Patrick Ohly patrick.o...@intel.com wrote:
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).
Two questions:
1) Do enough host distributions
