summaryrefslogtreecommitdiff
path: root/licenses/xz.txt
diff options
context:
space:
mode:
authorDavid Oberhollenzer <david.oberhollenzer@sigma-star.at>2019-11-24 13:49:55 +0100
committerDavid Oberhollenzer <david.oberhollenzer@sigma-star.at>2019-11-24 14:15:02 +0100
commitc84f61809335e0408f54cb2f11087785e4a1818c (patch)
tree78edb1fa4a20ead3ffb3ce33fab5b6734c166174 /licenses/xz.txt
parentad3d0728827d28b4d991730adf4abd2dd5bdda4a (diff)
Update README, clarify licensing situation
Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
Diffstat (limited to 'licenses/xz.txt')
-rw-r--r--licenses/xz.txt17
1 files changed, 17 insertions, 0 deletions
diff --git a/licenses/xz.txt b/licenses/xz.txt
new file mode 100644
index 0000000..99c125d
--- /dev/null
+++ b/licenses/xz.txt
@@ -0,0 +1,17 @@
+liblzma is in the public domain.
+
+You can do whatever you want with the files that have been put into
+the public domain. If you find public domain legally problematic,
+take the previous sentence as a license grant. If you still find
+the lack of copyright legally problematic, you have too many
+lawyers.
+
+As usual, this software is provided "as is", without any warranty.
+
+If you copy significant amounts of public domain code from XZ Utils
+into your project, acknowledging this somewhere in your software is
+polite (especially if it is proprietary, non-free software), but
+naturally it is not legally required. Here is an example of a good
+notice to put into "about box" or into documentation:
+
+ This software includes code from XZ Utils <https://tukaani.org/xz/>.