Merging upstream version 5.6.2.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 16 insertions, 14 deletions

diff --git a/PACKAGERS b/PACKAGERS
index 3042c66..b12c485 100644
--- a/PACKAGERS
+++ b/PACKAGERS
@@ -44,8 +44,8 @@ Information to packagers of XZ Utils
                         lzmadec binary for compatibility with LZMA Utils
         liblzma         liblzma.so.*
         liblzma-devel   liblzma.so, liblzma.a, API headers
-        liblzma-doc     Doxygen-generated liblzma API docs (HTML),
-                        example programs
+        liblzma-doc     Example programs and, if enabled at build time,
+                        Doxygen-generated liblzma API docs (HTML)
 
 
 2. Package description
@@ -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
@@ -169,13 +170,14 @@ Information to packagers of XZ Utils
     can be replaced with a symlink if your distro ships with shared
     copies of the common license texts.
 
-    The Doxygen-generated documentation (HTML) for the liblzma API
-    headers is included in the source release and will be installed by
-    "make install" to $docdir/api. All JavaScript is removed to
-    simplify license compliance and to reduce the install size. If the
-    liblzma API documentation is not desired, either run configure with
-    --disable-doc or remove the doc/api directory before running
-    "make install".
+    The Doxygen-generated liblzma API documentation (HTML) is built and
+    installed if the configure option --enable-doxygen is used (it's
+    disabled by default). This requires that Doxygen is available. The
+    API documentation is installed by "make install" to $docdir/api.
+
+        NOTE: The files generated by Doxygen include content from
+        Doxygen itself. Check the license info before distributing
+        the Doxygen-generated files.
 
 
 6. Extra files