<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 4 July 2015 at 12:38, Paul Eggleton <span dir="ltr"><<a href="mailto:paul.eggleton@linux.intel.com" target="_blank">paul.eggleton@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=":1ge" class="a3s" style="overflow:hidden">Well, at minimum for our purposes LGPLv3 (or LGPLv3+?) needs to be added to<br>
LICENSE in the nettle recipe (with &). Whether or not someone chooses to<br>
exclude that license in their configuration through INCOMPATIBLE_LICENSE is a<br>
completely separate matter (and that is, as you allude to, a distinct license<br>
from GPLv3).</div></blockquote></div><br>FWIW the YP documentation states to mark GPL LGPL and AGPL v3 in INCOMPATIBLE_LICENSE to build a GPLv3 image, on the rationale that the usual clauses that upset people are not specific to the GPL variation. The autobuilder just excludes GPL right now, but there's a bug to fix this.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Of course IANAL and the opinion of someone who actually does use INCOMPATIBLE_LICENSE to remove GPLv3 software would be appreciated!</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>