summaryrefslogtreecommitdiffstats
path: root/NEWS
diff options
context:
space:
mode:
authorDaniel Baumann <mail@daniel-baumann.ch>2015-11-07 14:04:50 +0000
committerDaniel Baumann <mail@daniel-baumann.ch>2015-11-07 14:04:50 +0000
commitb4fbba1e1c23c404b9e81ec1ad4fa703fbcdc0f4 (patch)
treeaaf89c31e25065d2f5a3b1d596b99029649d6f28 /NEWS
parentAdding upstream version 1.6~rc1. (diff)
downloadlzlib-b4fbba1e1c23c404b9e81ec1ad4fa703fbcdc0f4.tar.xz
lzlib-b4fbba1e1c23c404b9e81ec1ad4fa703fbcdc0f4.zip
Adding upstream version 1.6~rc2.upstream/1.6_rc2
Signed-off-by: Daniel Baumann <mail@daniel-baumann.ch>
Diffstat (limited to '')
-rw-r--r--NEWS24
1 files changed, 24 insertions, 0 deletions
diff --git a/NEWS b/NEWS
index 7207515..499140c 100644
--- a/NEWS
+++ b/NEWS
@@ -15,3 +15,27 @@ Minilzip now copies file dates, permissions, and ownership like "cp -p".
bits S_ISUID and S_ISGID are cleared).
"lzlib.texinfo" has been renamed to "lzlib.texi".
+
+The license has been changed to "GPL version 2 or later with link
+exception".
+
+ -----
+
+Rationale for the license change.
+
+I have recently been shocked to know that it is apparently not legal to
+use lzlib in GPLv2 programs. Linking those programs with lzlib violates
+the GPLv2. But linking proprietary programs with lzlib is fine and legal!
+
+This problem is not caused by any fault in lzlib's link exception; the
+LGPLv3 has the same problem. See for example
+http://nmav.gnutls.org/2013/03/the-perils-of-lgplv3.html
+
+Of course it was never my intention to prevent GPLv2 programs from using
+lzlib. I'm sorry for any inconveniences my oversight may have caused to
+distributions, GPLv2 software projects, and users in general.
+
+I am also ashamed of having participated in this schism of the GPL
+community. The mere proliferation of different free software licenses is
+a burden in and of itself. From now on I'll license all my projects and
+contributions in a way compatible with the GPLv2.