<br><br><div class="gmail_quote">On Fri, Dec 9, 2011 at 2:40 AM, Paul Eggleton <span dir="ltr"><<a href="mailto:paul.eggleton@linux.intel.com">paul.eggleton@linux.intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Friday 09 December 2011 11:30:40 Ulf Samuelsson wrote:<br>
> I think someone needs to sit down and do this in a structured manner.<br>
> A number of license files were modified.<br>
> For each file, the old checksum needs to be searched for in the tree,<br>
> and the license modified.<br>
<br>
</div>In case it wasn't clear I'm actually doing something which is not recommended<br>
in meta-opie since it provides none of the protection of LIC_FILES_CHKSUM and<br>
no small amount of fragility, as we have discovered. Nobody should really be<br>
doing this if they can possibly avoid it, and if they are then they shouldn't<br>
be too surprised when things break.<br></blockquote><div><br>Yes, I would suggest not pointing to the common-license directory as your LIC_FILES_CHECKSUM for a number of reasons, least of which is if one license text changes, things break. I would structure those recipes similar to gettext-native, by having the license in the recipe itself. And while the way it's structured is legitimate, it's probably not a good idea as eventually, we should be pulling those licenses at build time from the upstream provider of base OSI compliant licenses, <a href="http://spdx.org">spdx.org</a> and overlaying them on top of any non-OSI compliant licenses we maintain (Adobe, FSF-Unlimited...).<br>
<br>-b<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
FWIW, none of the recipes in OE-core itself (nor meta-oe for that matter)<br>
refer to files in the common license directory - I just checked.<br></blockquote><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><br> </div></blockquote><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
> A grep for "LICENSE =" should reveal offending recipes with "<recipe1><br>
> && <recipe2>"<br>
> or "<recipe1>/<recipe2>" etc.<br>
<br>
</div>This is a separate issue.<br>
<div class="HOEnZb"><div class="h5"><br>
Cheers,<br>
Paul<br>
<br>
--<br>
<br>
Paul Eggleton<br>
Intel Open Source Technology Centre<br>
</div></div></blockquote></div><br>-b<br clear="all"><br>-- <br>Elizabeth Flanagan<br>Yocto Project<br>Build and Release<br>