1 2XZ 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 Note: The JavaScript files (under the MIT license) have 25 been removed from the Doxygen-generated HTML version of the 26 liblzma API documentation. Doxygen itself is under the GNU GPL 27 but the remaining files generated by Doxygen are not affected 28 by the licenses used in Doxygen because Doxygen licensing has 29 the following exception: 30 31 "Documents produced by doxygen are derivative works 32 derived from the input used in their production; 33 they are not affected by this license." 34 35 - Translated messages are in the public domain. 36 37 - The build system contains public domain files, and files that 38 are under GNU GPLv2+ or GNU GPLv3+. None of these files end up 39 in the binaries being built. 40 41 - Test files and test code in the tests directory, and debugging 42 utilities in the debug directory are in the public domain. 43 44 - The extra directory may contain public domain files, and files 45 that are under various free software licenses. 46 47 You can do whatever you want with the files that have been put into 48 the public domain. If you find public domain legally problematic, 49 take the previous sentence as a license grant. If you still find 50 the lack of copyright legally problematic, you have too many 51 lawyers. 52 53 As usual, this software is provided "as is", without any warranty. 54 55 If you copy significant amounts of public domain code from XZ Utils 56 into your project, acknowledging this somewhere in your software is 57 polite (especially if it is proprietary, non-free software), but 58 naturally it is not legally required. Here is an example of a good 59 notice to put into "about box" or into documentation: 60 61 This software includes code from XZ Utils <https://tukaani.org/xz/>. 62 63 The following license texts are included in the following files: 64 - COPYING.LGPLv2.1: GNU Lesser General Public License version 2.1 65 - COPYING.GPLv2: GNU General Public License version 2 66 - COPYING.GPLv3: GNU General Public License version 3 67 68 Note that the toolchain (compiler, linker etc.) may add some code 69 pieces that are copyrighted. Thus, it is possible that e.g. liblzma 70 binary wouldn't actually be in the public domain in its entirety 71 even though it contains no copyrighted code from the XZ Utils source 72 package. 73 74 If you have questions, don't hesitate to ask the author(s) for more 75 information. 76 77