<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 29 November 2016 at 10:47, Robert P. J. Day <span dir="ltr"><<a href="mailto:rpjday@crashcourse.ca" target="_blank">rpjday@crashcourse.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":1ah" class="a3s aXjCH m158afb4091cd875a">one example i mentioned is that the YP guide does not list "sed" as a<br>
build host requirement, but "sed-native" is in ASSUME_PROVIDED;<br>
however, it's not listed in SANITY_REQUIRED_UTILITIES. that seems<br>
inconsistent.<br>
<div class="HOEnZb"></div></div></blockquote></div><br>It would be somewhat useful if there where a way to annotate in recipes what binary to check for on the host, so just doing ASSUME_PROVIDED=sed-native would look up in the sed recipe to check that "sed" exists on the host, so that SANITY_REQUIRED_UTILITIES doesn't need to be maintained separately.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Very low hanging fruit though. Patches welcome!</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>