<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 26, 2015 at 7:19 AM, Christopher Larson <span dir="ltr"><<a href="mailto:clarson@kergoth.com" target="_blank">clarson@kergoth.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><div class="gmail_quote">On Wed, Aug 26, 2015 at 4:01 AM, Burton, Ross <span dir="ltr"><<a 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"><span><div class="gmail_quote">On 26 August 2015 at 09:44, Joshua Lock <span dir="ltr"><<a href="mailto:joshua.lock@collabora.co.uk" target="_blank">joshua.lock@collabora.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="overflow:hidden">I do all of my builds on a separate partition in a directory hierarchy which is owned by my user - if I'm understanding this correctly I'll get QA WARNINGS for all of my builds with this change?<br></div></blockquote></div><br></span>The paths are prefixed with ${D} so pretend the commit log says "in packages".</blockquote></div><br></span>Heh, indeed, it's a package QA test. do_install runs under pseudo, so any newly created files there, or files chown'd to root, will be fine. If, however, a recipe does a cp -a or so to install without doing a chown, you'll end up with files in your rootfs owned by the user that did the build -- not good.</blockquote></div><br>I can re-submit with that commit message clarification, if needed? I rather thought the fact that it was in insane.bbclass, not sanity.bbclass, carried the necessary implication.<br>-- <br><div class="gmail_signature">Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div>
</div></div>