<div style="text-align:center"><div align="left" style="font-family:'Times New Roman';font-size:medium"><br></div></div><div class="gmail_quote">On Tue, Jan 10, 2012 at 18:34, Chris 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"><div>On Tue, Jan 10, 2012 at 9:12 AM, Andrei Gherzan <<a href="mailto:andrei@gherzan.ro" target="_blank">andrei@gherzan.ro</a>> wrote:<br>
> No worries. Anyway, you are right about the "+" mechanism but right now this<br>
> is a fast and complete solution.<br>
<br>
</div>Indeed, nice work on this.<br>
<span><font color="#888888">--<br>
Christopher Larson<br>
<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">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>
</font></span></blockquote></div><div><br></div><div>On Tue, Jan 10, 2012 at 19:05, Chris 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-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>On Tue, Jan 10, 2012 at 9:55 AM, Flanagan, Elizabeth<br><<a href="mailto:elizabeth.flanagan@intel.com" target="_blank">elizabeth.flanagan@intel.com</a>> wrote:<br>> Agreed! </div></blockquote></div><br><div>
Thank you.</div>
<div><br></div><div><br><br><div class="gmail_quote">On Tue, Jan 10, 2012 at 19:05, Chris 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-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>On Tue, Jan 10, 2012 at 9:55 AM, Flanagan, Elizabeth<br><<a href="mailto:elizabeth.flanagan@intel.com" target="_blank">elizabeth.flanagan@intel.com</a>> wrote:<br>> Agreed! One note about "+". There is still a discussion about "or<br>
> greater" licensing within the SPDX community about how "or greater"<br>> should be dealt with.<br>><br>> <a href="http://www.spdx.org/wiki/proposal-2010-11-16-1-or-later-version-licensing" target="_blank">http://www.spdx.org/wiki/proposal-2010-11-16-1-or-later-version-licensing</a><br>
> <a href="https://bugs.linuxfoundation.org/show_bug.cgi?id=591" target="_blank">https://bugs.linuxfoundation.org/show_bug.cgi?id=591</a><br><br></div>Interesting.<br><div><br>> I'm partial to, as a stop gap, re-including L/GPL-x.0+ license files<br>
> into common-licenses until they hash it out and treating "+" as just<br>> part of the license name. It's not a perfect solution but it should<br>> solve most "or greater" use cases.<br>
<br>
</div>I've been thinking about something like this.<br><br>LICENSE_EXPANSIONS += "GPL-2.0+:GPL-2.0,GPL-3.0"<br><br>Then process the license, turning GPL-2.0+ into an OR operation.<br>Replace with (GPL-2.0 | GPL-3.0).<br>
<br>Perhaps coupled with something like <a href="https://gist.github.com/1590028" target="_blank">https://gist.github.com/1590028</a> to<br>express distributor preferences, we then get a sanitized, SDPX, flat<br>string with the licenses we're going to be using for this. Then we run<br>
this against each binary package's LICENSE (if different than recipe)<br>and ensure our emitted binary packages match up with our license<br>choices.<br><div><div>--<br>Christopher Larson<br>
<br>_______________________________________________<br>Openembedded-core mailing list<br><a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">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>
</div><div><br></div></div></blockquote><div><br></div><div>Christopher's solution crossed my mind as well. Actually i tried something like this but i didn't want to modify more from this patch and i didn't really know how to define those expansions.</div>
<div>Another problem here that i faced and dropped the idea for, was the the scenario where a developer wants to exclude only GPLv3+. This case needed a another couple of "if"s and so on.</div><div><br></div><div>
So my solution seemed to deal most of the situations even if it looks a little... childish. </div></div></div>