<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 1, 2015 at 4:11 PM, Alex Franco <span dir="ltr"><<a href="mailto:alejandro.franco@linux.intel.com" target="_blank">alejandro.franco@linux.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=":1g4" class="a3s" style="overflow:hidden">I gather the original reason (for the sanity test, as well as these changes) is that it is better for everything under BUILDDIR - and certainly TMPDIR to be owned by the user running <span class="il">bitbake</span> and have standard permissions, the sticky <span class="il">bit</span> itself would prevent a user running <span class="il">bitbake</span>, even with +rwx permissions, from making changes to items it might need to manipulate, if those are not owned by this user. Similarly setuid and setgid might propagate user/group ownerships different from the user <span class="il">bitbake</span> is running as, into BUILDDIR and TMPDIR (and items therein).<br>
<br>
For more info take a look at: <a href="https://bugzilla.yoctoproject.org/show_bug.cgi?id=7669" rel="noreferrer" target="_blank">https://bugzilla.yoctoproject.org/show_bug.cgi?id=7669</a><br>
<br>
Perhaps there are more pressing reasons, perhaps Christopher Larson can comment a <span class="il">bit</span> on this.</div></blockquote></div><br>Indeed, the g+s can flow down into the files put into the packages, and then into the rootfs. I ran into a this problem quite a bit, since my project areas are in a g+s area to keep the files accessible to the group.<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>