<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
#2 seems more ubiquitous<br>
<br>
Franco<br>
<br>
<div class="moz-cite-prefix">On 10/19/2015 11:11 AM, Burton, Ross
wrote:<br>
</div>
<blockquote
cite="mid:CAJTo0LZhMs6Pr85oq2H_Tut12yx_f1JEbM+nsWpVOf1UC98ABg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On 19 October 2015 at 16:37, Burton,
Ross <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ross.burton@intel.com" target="_blank">ross.burton@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>Not sure what to do here. If we install file-native
directly into the sysroot we get occasional races on the
file binary causing build failures. If we make
file-native ASSUME_PROVIDED then rpm (and subversion)
change their behaviour depending on the presence of
libmagic-dev on the host (well, rpm4 requires libmagic,
rpm5 and subversion change their configuration).</div>
</blockquote>
</div>
<br>
Two proposals:</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">1) Tell RPM and Subversion to
explicitly enable libmagic support so they fail if
libmagic-dev isn't installed on the host, and document that
libmagic-dev is a build requirement</div>
<div class="gmail_extra">2) Change file-replacement-native to
install libmagic, and add file-replacement-native as a
dependency to subversion-native and rpm-native.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Does anyone have a strong opinion
either way?</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Ross</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>