<div dir="ltr">I'm good with that. I kept running into that scenario. Discussions about GPL but not LGPL.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 25, 2019 at 3:34 PM Smith, McCoy <<a href="mailto:mccoy.smith@intel.com">mccoy.smith@intel.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_-4279954640823039146WordSection1">
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Here’s what FSF says about incompatibility:
</span><a href="https://www.gnu.org/licenses/license-list.html#apache2" target="_blank">https://www.gnu.org/licenses/license-list.html#apache2</a><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,78,121)">It discusses GPLv3 (compatible) & GPLv2 (incompatible) but not LGPL.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,78,121)">FWIW John Sullivan is looking to update the FSF FAQ and this is issue he might want
to write a new FAQ on. Do you mind if I share this thread with him?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,78,121)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,78,121)"><u></u> <u></u></span></p>
<p class="MsoNormal"><a name="m_-4279954640823039146__MailEndCompose"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></a></p>
<p class="MsoNormal"><a name="m_-4279954640823039146______replyseparator"></a><b><span style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif"> License-discuss [mailto:<a href="mailto:license-discuss-bounces@lists.opensource.org" target="_blank">license-discuss-bounces@lists.opensource.org</a>]
<b>On Behalf Of </b>Bruce Perens via License-discuss<br>
<b>Sent:</b> Thursday, April 25, 2019 1:25 PM<br>
<b>To:</b> Bryan Christ <<a href="mailto:bryan.christ@gmail.com" target="_blank">bryan.christ@gmail.com</a>><br>
<b>Cc:</b> Bruce Perens <<a href="mailto:bruce@perens.com" target="_blank">bruce@perens.com</a>>; <a href="mailto:license-discuss@lists.opensource.org" target="_blank">license-discuss@lists.opensource.org</a><br>
<b>Subject:</b> Re: [License-discuss] Question about LGPL 2.1 and APL 2.0 Compatibility<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Well, obviously the Apache license permits these things, so no concern regarding your question.<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">A proprietary license that entirely prohibited modification to the extent of preventing re-linking with a modified LGPL library, or that prevented the reverse-engineering necessary to debug that modification, would not be compatible with
LGPL 2.1 . <u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Thu, Apr 25, 2019 at 1:22 PM Bryan Christ <<a href="mailto:bryan.christ@gmail.com" target="_blank">bryan.christ@gmail.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">Sorry for being dense here, but can you explain this a bit more?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal"><span style="color:black">And I didn't completely state all of the requirements of LGPL 2.1 on the non-LGPL piece:</span><span style="font-size:15pt;color:black"> <i>the terms </i>[must]<i> permit modification of the work for the customer's
own use and reverse engineering for debugging such modifications.</i></span><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Thu, Apr 25, 2019 at 2:42 PM Bruce Perens <<a href="mailto:bruce@perens.com" target="_blank">bruce@perens.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">It's definitely relevant between APL and <b>GPL</b>, because GPL places requirements that the terms of the
<i>entire</i> work do not include restrictions beyond those in the GPL. LGPL doesn't say that.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">And I didn't completely state all of the requirements of LGPL 2.1 on the non-LGPL piece:<span style="font-size:15pt"> <i>the terms
</i>[must]<i> permit modification of the work for the customer's own use and reverse engineering for debugging such modifications.</i></span><u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Thu, Apr 25, 2019 at 12:29 PM Bryan Christ <<a href="mailto:bryan.christ@gmail.com" target="_blank">bryan.christ@gmail.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">I came across a discussion about a patent clause contention between APL 2.0 and LGPL 2.1 and wasn't sure how/if that was relevant.<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Thu, Apr 25, 2019 at 2:26 PM Bruce Perens via License-discuss <<a href="mailto:license-discuss@lists.opensource.org" target="_blank">license-discuss@lists.opensource.org</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">Yes to both. For the same reasons you could link both to proprietary software. Neither license applies terms to works they are combined with, except for lgpl requiring that it is possible to upgrade or modify the lgpl software and for the
combination to be capable of being relinked. Was there any particular reason that you thought this might not be possible?<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Bruce<u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12pt"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Thu, Apr 25, 2019, 11:04 Bryan Christ <<a href="mailto:bryan.christ@gmail.com" target="_blank">bryan.christ@gmail.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">I am the author of a library that is licensed under the LGPL 2.1. It's very clear that a closed source work can dynamically link to the library. That's easy to understand. There are 2 other scenarios however that I am unclear about:<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">1. Can a LGPL 2.1 dynamically link to an APL 2.0 library or binary?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">2. Can an APL 2.0 binary dynamically link to a LGPL 2.1 library?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I did a lot of searching on the web first and couldn't find anything covering this.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks in advance to whoever replies.<br clear="all">
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">-- <u></u><u></u></p>
<div>
<p class="MsoNormal">Bryan<br>
<><<u></u><u></u></p>
</div>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
License-discuss mailing list<br>
<a href="mailto:License-discuss@lists.opensource.org" target="_blank">License-discuss@lists.opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org" target="_blank">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a><u></u><u></u></p>
</blockquote>
</div>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
License-discuss mailing list<br>
<a href="mailto:License-discuss@lists.opensource.org" target="_blank">License-discuss@lists.opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org" target="_blank">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">-- <u></u><u></u></p>
<div>
<p class="MsoNormal">Bryan<br>
<><<u></u><u></u></p>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">-- <u></u><u></u></p>
<div>
<p class="MsoNormal">Bryan<br>
<><<u></u><u></u></p>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">Bryan<br><><</div>