| 1 |
|
| 2 |
XZ Utils Licensing |
| 3 |
================== |
| 4 |
|
| 5 |
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!): |
| 8 |
|
| 9 |
- liblzma is in the public domain. |
| 10 |
|
| 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+. |
| 15 |
|
| 16 |
- 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+. |
| 19 |
|
| 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. |
| 23 |
|
| 24 |
- Translated messages are in the public domain. |
| 25 |
|
| 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. |
| 29 |
|
| 30 |
- Test files and test code in the tests directory, and debugging |
| 31 |
utilities in the debug directory are in the public domain. |
| 32 |
|
| 33 |
- The extra directory may contain public domain files, and files |
| 34 |
that are under various free software licenses. |
| 35 |
|
| 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. |
| 41 |
|
| 42 |
As usual, this software is provided "as is", without any warranty. |
| 43 |
|
| 44 |
If you copy significant amounts of public domain code from XZ Utils |
| 45 |
into your project, acknowledging this somewhere in your software is |
| 46 |
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: |
| 49 |
|
| 50 |
This software includes code from XZ Utils <http://tukaani.org/xz/>. |
| 51 |
|
| 52 |
The following license texts are included in the following files: |
| 53 |
- COPYING.LGPLv2.1: GNU Lesser General Public License version 2.1 |
| 54 |
- COPYING.GPLv2: GNU General Public License version 2 |
| 55 |
- COPYING.GPLv3: GNU General Public License version 3 |
| 56 |
|
| 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. |