COPYING 3.8 KB

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