File: NEWS

package info (click to toggle)
lzlib 1.6-2
  • links: PTS, VCS
  • area: main
  • in suites: jessie, jessie-kfreebsd
  • size: 492 kB
  • ctags: 496
  • sloc: ansic: 4,183; sh: 326; makefile: 146
file content (41 lines) | stat: -rw-r--r-- 1,572 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
Changes in version 1.6:

Compression ratio of option -9 has been slightly increased.

The configure script now accepts the option "--disable-static".

Improved portability to BSD systems:

    The configure script now accepts the option "--disable-ldconfig".

    "make install" now ignores any errors from ldconfig.

Minilzip now copies file dates, permissions, and ownership like "cp -p".
(If the user ID or the group ID can't be duplicated, the file permission
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.