<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 10, 2015, at 9:22 AM, Burton, Ross <<a href="mailto:ross.burton@intel.com" class="">ross.burton@intel.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On 7 August 2015 at 21:18, Khem Raj <span dir="ltr" class=""><<a href="mailto:raj.khem@gmail.com" target="_blank" class="">raj.khem@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":1zz" class="a3s" style="overflow:hidden">its GPLv3 with autoconf exception but the GPLv2 copy of recipe<br class="">
is left in as well to not break non-GPLv3 builds</div></blockquote></div><br class="">As the files in this are only used to configure the build, could it be whitelisted to allow it to be used in a no-GPLv3 build?</div><div class="gmail_extra"><br class=""></div></div></div></blockquote><div><br class=""></div><div>it could be. Remember its GPLv3 with autoconf exception but still its a new license for folks to use</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra">Ross</div></div>
</div></blockquote></div><br class=""></body></html>