| 1 |
Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ |
| 2 |
Upstream-Name: uuid |
| 3 |
Upstream-Contact: Boian Tzonev <[email protected]> |
| 4 |
Source: http://www.dardoria.net/software/uuid.html |
| 5 |
|
| 6 |
Files: * |
| 7 |
Copyright: 2007-2011 Boian Tzonev |
| 8 |
License: Lisp-LGPL-2.1 |
| 9 |
Preamble to the Gnu Lesser General Public License |
| 10 |
. |
| 11 |
The concept of the GNU Lesser General Public License version 2.1 |
| 12 |
("LGPL") has been adopted to govern the use and distribution of |
| 13 |
above-mentioned application. However, the LGPL uses terminology that is |
| 14 |
more appropriate for a program written in C than one written in |
| 15 |
Lisp. Nevertheless, the LGPL can still be applied to a Lisp program if |
| 16 |
certain clarifications are made. This document details those |
| 17 |
clarifications. Accordingly, the license for the open-source Lisp |
| 18 |
applications consists of this document plus the LGPL. Wherever there is |
| 19 |
a conflict between this document and the LGPL, this document takes |
| 20 |
precedence over the LGPL. |
| 21 |
. |
| 22 |
A "Library" in Lisp is a collection of Lisp functions, data and foreign |
| 23 |
modules. The form of the Library can be Lisp source code (for processing |
| 24 |
by an interpreter) or object code (usually the result of compilation of |
| 25 |
source code or built with some other mechanisms). Foreign modules are |
| 26 |
object code in a form that can be linked into a Lisp executable. When we |
| 27 |
speak of functions we do so in the most general way to include, in |
| 28 |
addition, methods and unnamed functions. Lisp "data" is also a general |
| 29 |
term that includes the data structures resulting from defining Lisp |
| 30 |
classes. A Lisp application may include the same set of Lisp objects as |
| 31 |
does a Library, but this does not mean that the application is |
| 32 |
necessarily a "work based on the Library" it contains. |
| 33 |
. |
| 34 |
The Library consists of everything in the distribution file set before |
| 35 |
any modifications are made to the files. If any of the functions or |
| 36 |
classes in the Library are redefined in other files, then those |
| 37 |
redefinitions ARE considered a work based on the Library. If additional |
| 38 |
methods are added to generic functions in the Library, those additional |
| 39 |
methods are NOT considered a work based on the Library. If Library |
| 40 |
classes are subclassed, these subclasses are NOT considered a work based |
| 41 |
on the Library. If the Library is modified to explicitly call other |
| 42 |
functions that are neither part of Lisp itself nor an available add-on |
| 43 |
module to Lisp, then the functions called by the modified Library ARE |
| 44 |
considered a work based on the Library. The goal is to ensure that the |
| 45 |
Library will compile and run without getting undefined function errors. |
| 46 |
. |
| 47 |
It is permitted to add proprietary source code to the Library, but it |
| 48 |
must be done in a way such that the Library will still run without that |
| 49 |
proprietary code present. Section 5 of the LGPL distinguishes between |
| 50 |
the case of a library being dynamically linked at runtime and one being |
| 51 |
statically linked at build time. Section 5 of the LGPL states that the |
| 52 |
former results in an executable that is a "work that uses the Library." |
| 53 |
Section 5 of the LGPL states that the latter results in one that is a |
| 54 |
"derivative of the Library", which is therefore covered by the |
| 55 |
LGPL. Since Lisp only offers one choice, which is to link the Library |
| 56 |
into an executable at build time, we declare that, for the purpose |
| 57 |
applying the LGPL to the Library, an executable that results from |
| 58 |
linking a "work that uses the Library" with the Library is considered a |
| 59 |
"work that uses the Library" and is therefore NOT covered by the LGPL. |
| 60 |
. |
| 61 |
Because of this declaration, section 6 of LGPL is not applicable to the |
| 62 |
Library. However, in connection with each distribution of this |
| 63 |
executable, you must also deliver, in accordance with the terms and |
| 64 |
conditions of the LGPL, the source code of Library (or your derivative |
| 65 |
thereof) that is incorporated into this executable. |
| 66 |
. |
| 67 |
On Debian systems, the text of the LGPL is in |
| 68 |
/usr/share/common-licenses/LGPL-2.1. |
| 69 |
|
| 70 |
Files: debian/* |
| 71 |
Copyright: 2014 Dimitri Fontaine |
| 72 |
License: WTFPL |
| 73 |
DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE |
| 74 |
Version 2, December 2004 |
| 75 |
. |
| 76 |
Copyright (C) 2014 Dimitri Fontaine <[email protected]> |
| 77 |
. |
| 78 |
Everyone is permitted to copy and distribute verbatim or modified |
| 79 |
copies of this license document, and changing it is allowed as long |
| 80 |
as the name is changed. |
| 81 |
. |
| 82 |
DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE |
| 83 |
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION |
| 84 |
. |
| 85 |
0. You just DO WHAT THE FUCK YOU WANT TO. |