COPYING 4.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100
  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 under the BSD Zero Clause License (0BSD).
  7. - The command line tools xz, xzdec, lzmadec, and lzmainfo are
  8. under 0BSD except that, on systems that don't have a usable
  9. getopt_long, GNU getopt_long is compiled and linked in from the
  10. 'lib' directory. The getopt_long code is under GNU LGPLv2.1+.
  11. - The scripts to grep, diff, and view compressed files have been
  12. adapted from GNU gzip. These scripts (xzgrep, xzdiff, xzless,
  13. and xzmore) are under GNU GPLv2+. The man pages of the scripts
  14. are under 0BSD; they aren't based on the man pages of GNU gzip.
  15. - Most of the XZ Utils specific documentation that is in
  16. plain text files (like README, INSTALL, PACKAGERS, NEWS,
  17. and ChangeLog) are under 0BSD unless stated otherwise in
  18. the file itself. The files xz-file-format.txt and
  19. lzma-file-format.xt are in the public domain but may
  20. be distributed under the terms of 0BSD too.
  21. - Doxygen-generated HTML version of the liblzma API documentation:
  22. While Doxygen is under the GNU GPLv2, the license information
  23. in Doxygen includes the following exception:
  24. Documents produced by doxygen are derivative works
  25. derived from the input used in their production;
  26. they are not affected by this license.
  27. Note: The JavaScript files (under the MIT license) have
  28. been removed from the Doxygen output.
  29. - The XZ logo (xz-logo.png) included in the Doxygen-generated
  30. documentation is under the Creative Commons BY-SA 4.0 license.
  31. - Translated messages and man pages are under 0BSD except that
  32. some old translations are in the public domain.
  33. - Test files and test code in the 'tests' directory, and
  34. debugging utilities in the 'debug' directory are under
  35. the BSD Zero Clause License (0BSD).
  36. - The GNU Autotools based build system contains files that are
  37. under GNU GPLv2+, GNU GPLv3+, and a few permissive licenses.
  38. These files don't affect the licensing of the binaries being
  39. built.
  40. - The extra directory contain files that are under various
  41. free software licenses.
  42. For the files under the BSD Zero Clause License (0BSD), if
  43. a copyright notice is needed, the following is sufficient:
  44. Copyright (C) The XZ Utils authors and contributors
  45. If you copy significant amounts of 0BSD-licensed code from XZ Utils
  46. into your project, acknowledging this somewhere in your software is
  47. polite (especially if it is proprietary, non-free software), but
  48. it is not legally required by the license terms. Here is an example
  49. of a good notice to put into "about box" or into documentation:
  50. This software includes code from XZ Utils
  51. <https://xz.tukaani.org/xz-utils/>.
  52. The following license texts are included in the following files:
  53. - COPYING.0BSD: BSD Zero Clause License
  54. - COPYING.LGPLv2.1: GNU Lesser General Public License version 2.1
  55. - COPYING.GPLv2: GNU General Public License version 2
  56. - COPYING.GPLv3: GNU General Public License version 3
  57. - COPYING.CC-BY-SA-4.0: Creative Commons Attribution-ShareAlike 4.0
  58. International Public License
  59. A note about old XZ Utils releases:
  60. XZ Utils releases 5.4.6 and older and 5.5.1alpha have a
  61. significant amount of code put into the public domain and
  62. that obviously remains so. The switch from public domain to
  63. 0BSD for newer releases was made in Febrary 2024 because
  64. public domain has (real or perceived) legal ambiguities in
  65. some jurisdictions.
  66. There is very little *practical* difference between public
  67. domain and 0BSD. The main difference likely is that one
  68. shouldn't claim that 0BSD-licensed code is in the public
  69. domain; 0BSD-licensed code is copyrighted but available under
  70. an extremely permissive license. Neither 0BSD nor public domain
  71. require retaining or reproducing author, copyright holder, or
  72. license notices when distributing the software. (Compare to,
  73. for example, BSD 2-Clause "Simplified" License which does have
  74. such requirements.)
  75. If you have questions, don't hesitate to ask for more information.
  76. The contact information is in the README file.