diff options
author | Lasse Collin <lasse.collin@tukaani.org> | 2024-02-12 17:09:10 +0200 |
---|---|---|
committer | Lasse Collin <lasse.collin@tukaani.org> | 2024-02-14 18:31:12 +0200 |
commit | 689e0228baeb95232430e90d628379db89583d71 (patch) | |
tree | 1ac08f6030261327d8bc231adf1ab3e16f623645 /PACKAGERS | |
parent | Fix SHA-256 authors. (diff) | |
download | xz-689e0228baeb95232430e90d628379db89583d71.tar.xz |
Change most public domain parts to 0BSD.
Translations and doc/xz-file-format.txt and doc/lzma-file-format.txt
were not touched.
COPYING.0BSD was added.
Diffstat (limited to '')
-rw-r--r-- | PACKAGERS | 11 |
1 files changed, 6 insertions, 5 deletions
@@ -124,14 +124,15 @@ Information to packagers of XZ Utils If the package manager supports a license field, you probably should put GPLv2+ there (GNU GPL v2 or later). The interesting parts of - XZ Utils are in the public domain, but some less important files - ending up into the binary package are under GPLv2+. So it is simplest - to just say GPLv2+ if you cannot specify "public domain and GPLv2+". + XZ Utils are under the BSD Zero Clause License (0BSD), but some less + important files ending up into the binary package are under GPLv2+. + So it is simplest to just say GPLv2+ if you cannot specify + "BSD0 and GPLv2+". If you split XZ Utils into multiple packages as described earlier in this file, liblzma and liblzma-dev packages will contain only - public domain code (from XZ Utils at least; compiler or linker may - add some third-party code, which may be copyrighted). + 0BSD-licensed code from XZ Utils (compiler or linker may add some + third-party code which may have other licenses). 4. configure options |