<br><br><div class="gmail_quote">On Fri, Dec 9, 2011 at 5:51 AM, Koen Kooi <span dir="ltr"><<a href="mailto:koen@dominion.thruhere.net">koen@dominion.thruhere.net</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;">
<br>
Op 9 dec. 2011, om 14:46 heeft Ulf Samuelsson het volgende geschreven:<br>
<div><div class="h5"><br>
> On 2011-12-09 12:45, Richard Purdie wrote:<br>
>> On Fri, 2011-12-09 at 03:21 +0100, Ulf Samuelsson wrote:<br>
>>> On 2011-12-07 22:53, Khem Raj wrote:<br>
>>>> On (07/12/11 11:34), Beth Flanagan wrote:<br>
>>>>> From: Christopher Larson<<a href="mailto:kergoth@gmail.com">kergoth@gmail.com</a>><br>
>>>>><br>
>>>>> Deploys sources for recipes for compliance with copyleft-style licenses<br>
>>>>> Defaults to using symlinks, as it's a quick operation, and one can easily<br>
>>>>> follow the links when making use of the files (e.g. tar with the -h arg).<br>
>>>>><br>
>>>>> By default, includes all GPL and LGPL, and excludes CLOSED and Proprietary.<br>
>>>>><br>
>>>>> Signed-off-by: Christopher Larson<<a href="mailto:kergoth@gmail.com">kergoth@gmail.com</a>><br>
>>>>> ---<br>
>>>>> meta/classes/copyleft_compliance.bbclass | 94 ++++++++++++++++++++++++++++++<br>
>>>>> 1 files changed, 94 insertions(+), 0 deletions(-)<br>
>>>>> create mode 100644 meta/classes/copyleft_compliance.bbclass<br>
>>>>><br>
>>>>> diff --git a/meta/classes/copyleft_compliance.bbclass b/meta/classes/copyleft_compliance.bbclass<br>
>>>>> new file mode 100644<br>
>>>>> index 0000000..5d9ab11<br>
>>>>> --- /dev/null<br>
>>>>> +++ b/meta/classes/copyleft_compliance.bbclass<br>
>>>>> @@ -0,0 +1,94 @@<br>
>>>>> +# Deploy sources for recipes for compliance with copyleft-style licenses<br>
>>>>> +# Defaults to using symlinks, as it's a quick operation, and one can easily<br>
>>>>> +# follow the links when making use of the files (e.g. tar with the -h arg).<br>
>>>>> +#<br>
>>>>> +# By default, includes all GPL and LGPL, and excludes CLOSED and Proprietary.<br>
>>>>> +#<br>
>>>>> +# vi:sts=4:sw=4:et<br>
>>>>> +<br>
>>>>> +COPYLEFT_SOURCES_DIR ?= '${DEPLOY_DIR}/copyleft_sources'<br>
>>>>> +<br>
>>>>> +COPYLEFT_LICENSE_INCLUDE ?= 'GPL* LGPL*'<br>
>>>>> +COPYLEFT_LICENSE_INCLUDE[type] = 'list'<br>
>>>>> +COPYLEFT_LICENSE_INCLUDE[doc] = 'Space separated list of globs which include licenses'<br>
>>> If the Ampersand is not accepted in the LICENSE string, then the recipes<br>
>>> below are broken.<br>
>>><br>
>>> From my latest build, at least recipes with "&&" fail...<br>
>>> This means that nothing really completes that I have tested.<br>
>>><br>
>>> MAJOR BREAKAGE!!!!<br>
>>><br>
>>> I think it would be better FIRST to fix the recipes, and then introduce<br>
>>> checking.<br>
>> I think the single ampersand is accepted, the double might no longer be.<br>
> Yes, the single ampersand works, but the double ampersand will break the build<br>
> as well as the slash '/'.<br>
><br>
><br>
>> Certainly oe-core does continue to work. I hadn't realised there were<br>
>> incompatibilities introduced by this patch :(<br>
>><br>
>> Not sure what we should do about this at this point, probably fix the<br>
>> layers :/.<br>
>><br>
> True, question is who and when ?<br>
<br>
</div></div>The people complaining about it and right now.<br></blockquote><div><br><br>I know there was a conversation a while back about standardizing this field and documenting it. If anything fell out of it, IDK, If there is any documentation for what is valid form, I've not seen it. If it exists, could someone point me to it? If it doesn't could we get a standards discussion going here about how to move forward with this so we have something documented? I've seen a bunch of different standards here and I really want to get something nailed down as trying to write code for a field that isn't well defined is a pain. <br>
<br>A few things I've been thinking about here.<br><br>- LICENSE should be ast parsable. <br>- license within LICENSE should have no spaces.<br>- At last count there are 100+ OSI opensource licenses. I've been pulling from <a href="http://spdx.org">spdx.org</a> and trying to use their naming convention while also supporting mappings to non-spdx naming conventions. However there are some LICENSE entries that are just wrong (GPL without a version) and need to be fixed. <br>
- the operands I've been supporting are & or |, with a modifier of +. I've also been supporting parens grouping of license. example: "(Foo-1.0 & Bar-1.0 ) | (Foo-2.0 & Bar-2.0)". <br>- There is an actual issue with LICENSE in that LICENSE is recipe based. We should probably discuss the ability to support LICENSE_pkg, because the recipe may contain multiple packages some of which don't share a license in LICENSE.<br>
- LICENSE priority should probably be dealt in a config but not in the recipe. To me, it would make more sense as the main use case would probably center around "If I can avoid getting XXX
license in this image, please do".<br>
<br>I'll look at this to see if there is a way to handle some of the issues this code introduces better, as I'm sure other 3rd party layers exist that will have the same issue with this.<br><br>-b<br><br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
-----BEGIN PGP SIGNATURE-----<br>
<br>
iEYEARECAAYFAk7iEksACgkQMkyGM64RGpEPYQCeMpX884EmuwpUaIdFrvJ4Pp09<br>
aPoAn08cOAO5X2JMPXSoOEcFBPzDt+0V<br>
=LDRp<br>
-----END PGP SIGNATURE-----<br>
<br>_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core" target="_blank">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Elizabeth Flanagan<br>Yocto Project<br>Build and Release<br>