<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 11 August 2015 at 09:44, Patrick Ohly <span dir="ltr"><<a href="mailto:patrick.ohly@intel.com" target="_blank">patrick.ohly@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":1vg" class="a3s" style="overflow:hidden">Installing "<span class="il">tar</span>" into the sysroot leads to race conditions<br>
(tasks which do not depend on <span class="il">tar</span>-<span class="il">replacement</span>-native may already<br>
call <span class="il">tar</span> while it's installation is incomplete). Avoid those<br>
by installing only the <span class="il">tar</span> binary under the name <span class="il">tar</span>-native.<br></div></blockquote></div><br>So the point of tar-replacement-native was that it's a *replacement* for the host tar, so it needs the same name. If it was to be installed as an opt-in alternative there's a mechanism for doing that already (see EXTRANATIVEPATH) but that would break the purpose of tar-replacement-native.</div><div class="gmail_extra"><br></div><div class="gmail_extra">I think for this situation you should show how to enable xattrs for images, with the caveat that if your host tar isn't suitable the user should bitbake just tar-replacement-native *first*.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>