COPYING 3.3 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576
  1. XZ Utils Licensing
  2. ==================
  3. Different licenses apply to different files in this package. Here
  4. is a rough summary of which licenses apply to which parts of this
  5. package (but check the individual files to be sure!):
  6. - liblzma is in the public domain.
  7. - xz, xzdec, and lzmadec command line tools are in the public
  8. domain unless GNU getopt_long had to be compiled and linked
  9. in from the lib directory. The getopt_long code is under
  10. GNU LGPLv2.1+.
  11. - The scripts to grep, diff, and view compressed files have been
  12. adapted from gzip. These scripts and their documentation are
  13. under GNU GPLv2+.
  14. - All the documentation in the doc directory and most of the
  15. XZ Utils specific documentation files in other directories
  16. are in the public domain.
  17. Note: The JavaScript files (under the MIT license) have
  18. been removed from the Doxygen-generated HTML version of the
  19. liblzma API documentation. Doxygen itself is under the GNU GPL
  20. but the remaining files generated by Doxygen are not affected
  21. by the licenses used in Doxygen because Doxygen licensing has
  22. the following exception:
  23. "Documents produced by doxygen are derivative works
  24. derived from the input used in their production;
  25. they are not affected by this license."
  26. - Translated messages are in the public domain.
  27. - The build system contains public domain files, and files that
  28. are under GNU GPLv2+ or GNU GPLv3+. None of these files end up
  29. in the binaries being built.
  30. - Test files and test code in the tests directory, and debugging
  31. utilities in the debug directory are in the public domain.
  32. - The extra directory may contain public domain files, and files
  33. that are under various free software licenses.
  34. You can do whatever you want with the files that have been put into
  35. the public domain. If you find public domain legally problematic,
  36. take the previous sentence as a license grant. If you still find
  37. the lack of copyright legally problematic, you have too many
  38. lawyers.
  39. As usual, this software is provided "as is", without any warranty.
  40. If you copy significant amounts of public domain code from XZ Utils
  41. into your project, acknowledging this somewhere in your software is
  42. polite (especially if it is proprietary, non-free software), but
  43. naturally it is not legally required. Here is an example of a good
  44. notice to put into "about box" or into documentation:
  45. This software includes code from XZ Utils <https://tukaani.org/xz/>.
  46. The following license texts are included in the following files:
  47. - COPYING.LGPLv2.1: GNU Lesser General Public License version 2.1
  48. - COPYING.GPLv2: GNU General Public License version 2
  49. - COPYING.GPLv3: GNU General Public License version 3
  50. Note that the toolchain (compiler, linker etc.) may add some code
  51. pieces that are copyrighted. Thus, it is possible that e.g. liblzma
  52. binary wouldn't actually be in the public domain in its entirety
  53. even though it contains no copyrighted code from the XZ Utils source
  54. package.
  55. If you have questions, don't hesitate to ask the author(s) for more
  56. information.