<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK][EFL] CryptoDigest implementation depends on GnuTLS with LGPLv3+/GPLv2+ deps"
href="https://bugs.webkit.org/show_bug.cgi?id=162913#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK][EFL] CryptoDigest implementation depends on GnuTLS with LGPLv3+/GPLv2+ deps"
href="https://bugs.webkit.org/show_bug.cgi?id=162913">bug 162913</a>
from <span class="vcard"><a class="email" href="mailto:clopez@igalia.com" title="Carlos Alberto Lopez Perez <clopez@igalia.com>"> <span class="fn">Carlos Alberto Lopez Perez</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=162913#c7">comment #7</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=162913#c0">comment #0</a>)
> > This makes WebKit GTK effectively LPGLv3+ when gnutls in linked in.
>
> Turns out we misunderstood how these licenses work. WebKitGTK+ is still
> effectively LGPLv2+ and we have no upstream problem. You just have to ensure
> you comply with the terms of either LGPLv3+ or GPLv2+ with respect to the
> dependent libraries. This is a problem for certain companies that do not
> wish to do so, so we still want to get rid of the GnuTLS dependency, but it
> no longer seems urgent.</span >
You can also comply with LGPLv2+ alone depending on how you build WebKitGTK+.
GnuTLS can be built with libgmp-4.2.1 and nettle-2.7.1. If you opt to do this, then everything is LGPLv2+.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>