@@ -3,63 +3,68 @@ XZ Utils Licensing
33==================
44
55 Different licenses apply to different files in this package. Here
6- is a rough summary of which licenses apply to which parts of this
7- package (but check the individual files to be sure!):
6+ is a summary of which licenses apply to which parts of this package:
87
9- - liblzma is in the public domain .
8+ - liblzma is under the BSD Zero Clause License (0BSD) .
109
11- - xz, xzdec, and lzmadec command line tools are in the public
12- domain unless GNU getopt_long had to be compiled and linked
13- in from the lib directory. The getopt_long code is under
14- GNU LGPLv2.1+.
10+ - The command line tools xz, xzdec, lzmadec, and lzmainfo are
11+ under 0BSD except that, on systems that don't have a usable
12+ getopt_long, GNU getopt_long is compiled and linked in from the
13+ 'lib' directory. The getopt_long code is under GNU LGPLv2.1+.
1514
1615 - The scripts to grep, diff, and view compressed files have been
17- adapted from gzip. These scripts and their documentation are
18- under GNU GPLv2+.
16+ adapted from GNU gzip. These scripts (xzgrep, xzdiff, xzless,
17+ and xzmore) are under GNU GPLv2+. The man pages of the scripts
18+ are under 0BSD; they aren't based on the man pages of GNU gzip.
1919
20- - All the documentation in the doc directory and most of the
21- XZ Utils specific documentation files in other directories
22- are in the public domain.
20+ - Most of the XZ Utils specific documentation that is in
21+ plain text files (like README, INSTALL, PACKAGERS, NEWS,
22+ and ChangeLog) are under 0BSD unless stated otherwise in
23+ the file itself. The files xz-file-format.txt and
24+ lzma-file-format.xt are in the public domain but may
25+ be distributed under the terms of 0BSD too.
2326
24- - Translated messages are in the public domain.
27+ - Translated messages and man pages are under 0BSD except that
28+ some old translations are in the public domain.
2529
26- - The build system contains public domain files, and files that
27- are under GNU GPLv2+ or GNU GPLv3+. None of these files end up
28- in the binaries being built .
30+ - Test files and test code in the 'tests' directory, and
31+ debugging utilities in the 'debug' directory are under
32+ the BSD Zero Clause License (0BSD) .
2933
30- - Test files and test code in the tests directory, and debugging
31- utilities in the debug directory are in the public domain.
34+ - The GNU Autotools based build system contains files that are
35+ under GNU GPLv2+, GNU GPLv3+, and a few permissive licenses.
36+ These files don't affect the licensing of the binaries being
37+ built.
3238
33- - The extra directory may contain public domain files, and files
34- that are under various free software licenses.
39+ - The 'extra' directory contains files that are under various
40+ free software licenses. These aren't built or installed as
41+ part of XZ Utils.
3542
36- You can do whatever you want with the files that have been put into
37- the public domain. If you find public domain legally problematic,
38- take the previous sentence as a license grant. If you still find
39- the lack of copyright legally problematic, you have too many
40- lawyers.
43+ The following command may be helpful in finding per-file license
44+ information. It works on xz.git and on a clean file tree extracted
45+ from a release tarball.
4146
42- As usual, this software is provided "as is", without any warranty.
47+ sh build-aux/license-check.sh -v
4348
44- If you copy significant amounts of public domain code from XZ Utils
49+ For the files under the BSD Zero Clause License (0BSD), if
50+ a copyright notice is needed, the following is sufficient:
51+
52+ Copyright (C) The XZ Utils authors and contributors
53+
54+ If you copy significant amounts of 0BSD-licensed code from XZ Utils
4555 into your project, acknowledging this somewhere in your software is
4656 polite (especially if it is proprietary, non-free software), but
47- naturally it is not legally required. Here is an example of a good
48- notice to put into "about box" or into documentation:
57+ it is not legally required by the license terms . Here is an example
58+ of a good notice to put into "about box" or into documentation:
4959
5060 This software includes code from XZ Utils <https://tukaani.org/xz/>.
5161
5262 The following license texts are included in the following files:
63+ - COPYING.0BSD: BSD Zero Clause License
5364 - COPYING.LGPLv2.1: GNU Lesser General Public License version 2.1
5465 - COPYING.GPLv2: GNU General Public License version 2
5566 - COPYING.GPLv3: GNU General Public License version 3
5667
57- Note that the toolchain (compiler, linker etc.) may add some code
58- pieces that are copyrighted. Thus, it is possible that e.g. liblzma
59- binary wouldn't actually be in the public domain in its entirety
60- even though it contains no copyrighted code from the XZ Utils source
61- package.
62-
63- If you have questions, don't hesitate to ask the author(s) for more
64- information.
68+ If you have questions, don't hesitate to ask for more information.
69+ The contact information is in the README file.
6570
0 commit comments