| 1 |
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ |
| 2 |
Upstream-Name: cl-puri |
| 3 |
Source: http://files.kpe.io/puri/ |
| 4 |
Upstream-Contact: Kevin M. Rosenberg <[email protected]> |
| 5 |
|
| 6 |
Files: * |
| 7 |
Copyright: 1986-2000 Franz Inc, Berkeley, CA |
| 8 |
2003 Kevin Rosenberg |
| 9 |
License: LGPL-2.1 |
| 10 |
|
| 11 |
Files: debian/* |
| 12 |
Copyright: 2003-2020 Kevin M. Rosenberg <[email protected]> |
| 13 |
License: LGPL-2.1 |
| 14 |
|
| 15 |
License: LGPL-2.1 |
| 16 |
This code is free software; you can redistribute it and/or modify it |
| 17 |
under the terms of the version 2.1 of the GNU Lesser General Public |
| 18 |
License as published by the Free Software Foundation, as clarified by |
| 19 |
the Franz preamble to the LGPL found in |
| 20 |
http://opensource.franz.com/preamble.html. The preambled is copied |
| 21 |
below. |
| 22 |
. |
| 23 |
This code is distributed in the hope that it will be useful, |
| 24 |
but without any warranty; without even the implied warranty of |
| 25 |
merchantability or fitness for a particular purpose. See the GNU |
| 26 |
Lesser General Public License for more details. |
| 27 |
. |
| 28 |
The GNU Lessor General Public License can be found in your Debian file |
| 29 |
system in /usr/share/common-licenses/LGPL-2.1. |
| 30 |
. |
| 31 |
Preamble to the Gnu Lesser General Public License |
| 32 |
------------------------------------------------- |
| 33 |
Copyright (c) 2000 Franz Incorporated, Berkeley, CA 94704 |
| 34 |
. |
| 35 |
The concept of the GNU Lesser General Public License version 2.1 |
| 36 |
("LGPL") has been adopted to govern the use and distribution of |
| 37 |
above-mentioned application. However, the LGPL uses terminology that |
| 38 |
is more appropriate for a program written in C than one written in |
| 39 |
Lisp. Nevertheless, the LGPL can still be applied to a Lisp program if |
| 40 |
certain clarifications are made. This document details those |
| 41 |
clarifications. Accordingly, the license for the open-source Lisp |
| 42 |
applications consists of this document plus the LGPL. Wherever there |
| 43 |
is a conflict between this document and the LGPL, this document takes |
| 44 |
precedence over the LGPL. |
| 45 |
. |
| 46 |
A "Library" in Lisp is a collection of Lisp functions, data and |
| 47 |
foreign modules. The form of the Library can be Lisp source code (for |
| 48 |
processing by an interpreter) or object code (usually the result of |
| 49 |
compilation of source code or built with some other |
| 50 |
mechanisms). Foreign modules are object code in a form that can be |
| 51 |
linked into a Lisp executable. When we speak of functions we do so in |
| 52 |
the most general way to include, in addition, methods and unnamed |
| 53 |
functions. Lisp "data" is also a general term that includes the data |
| 54 |
structures resulting from defining Lisp classes. A Lisp application |
| 55 |
may include the same set of Lisp objects as does a Library, but this |
| 56 |
does not mean that the application is necessarily a "work based on the |
| 57 |
Library" it contains. |
| 58 |
. |
| 59 |
The Library consists of everything in the distribution file set before |
| 60 |
any modifications are made to the files. If any of the functions or |
| 61 |
classes in the Library are redefined in other files, then those |
| 62 |
redefinitions ARE considered a work based on the Library. If |
| 63 |
additional methods are added to generic functions in the Library, |
| 64 |
those additional methods are NOT considered a work based on the |
| 65 |
Library. If Library classes are subclassed, these subclasses are NOT |
| 66 |
considered a work based on the Library. If the Library is modified to |
| 67 |
explicitly call other functions that are neither part of Lisp itself |
| 68 |
nor an available add-on module to Lisp, then the functions called by |
| 69 |
the modified Library ARE considered a work based on the Library. The |
| 70 |
goal is to ensure that the Library will compile and run without |
| 71 |
getting undefined function errors. |
| 72 |
. |
| 73 |
It is permitted to add proprietary source code to the Library, but it |
| 74 |
must be done in a way such that the Library will still run without |
| 75 |
that proprietary code present. Section 5 of the LGPL distinguishes |
| 76 |
between the case of a library being dynamically linked at runtime and |
| 77 |
one being statically linked at build time. Section 5 of the LGPL |
| 78 |
states that the former results in an executable that is a "work that |
| 79 |
uses the Library." Section 5 of the LGPL states that the latter |
| 80 |
results in one that is a "derivative of the Library", which is |
| 81 |
therefore covered by the LGPL. Since Lisp only offers one choice, |
| 82 |
which is to link the Library into an executable at build time, we |
| 83 |
declare that, for the purpose applying the LGPL to the Library, an |
| 84 |
executable that results from linking a "work that uses the Library" |
| 85 |
with the Library is considered a "work that uses the Library" and is |
| 86 |
therefore NOT covered by the LGPL. |
| 87 |
. |
| 88 |
Because of this declaration, section 6 of LGPL is not applicable to |
| 89 |
the Library. However, in connection with each distribution of this |
| 90 |
executable, you must also deliver, in accordance with the terms and |
| 91 |
conditions of the LGPL, the source code of Library (or your derivative |
| 92 |
thereof) that is incorporated into this executable. |