<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 9, 2015 at 5:38 AM, Mike Looijmans <span dir="ltr"><<a href="mailto:mike.looijmans@topic.nl" target="_blank">mike.looijmans@topic.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":2ah" class="a3s" style="overflow:hidden">Just posting a related idea here:<br>
<br>
There are quite a few recipes that just contain a bunch of (data) files, and use a simple "cp -r" in the install phase. Instead of peppering these with "chown" calls, it might be better to create a small utility that basically runs the "install" command recursively, and replace the "cp -r" with "install_recursive".<span class=""><br></span></div></blockquote></div><br>Something like that doesn't seem unreasonable, so the classes/recipes don't have to worry about the particulars of the recursive copy tool being used.</div><div class="gmail_extra"><br></div><div class="gmail_extra">That said, doesn't cp -r result in correct ownership, since the files are created without preserving permissions or ownership? I'm pretty sure it's the cp -a / cp -pPr that we need to be more concerned with.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Note that with gnu cp, it's possible to tell it to preserve permissions, but not ownership. It's not portable to non-gnu cp, but I don't know what we care about that anyway.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ex.: `cp -a --no-preserve=ownership`<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>