| 1 |
<html> |
|---|
| 2 |
|
|---|
| 3 |
<head> |
|---|
| 4 |
<title>Preamble to the Gnu Lesser General Public License</title> |
|---|
| 5 |
</head> |
|---|
| 6 |
|
|---|
| 7 |
<body> |
|---|
| 8 |
|
|---|
| 9 |
<h1>Preamble to the Gnu Lesser General Public License</h1> |
|---|
| 10 |
<p>Copyright (c) 2000 Franz Incorporated, Berkeley, CA 94704</p> |
|---|
| 11 |
<p> |
|---|
| 12 |
The concept of the |
|---|
| 13 |
<a href="license.html"> |
|---|
| 14 |
GNU Lesser General Public License version 2.1</a> |
|---|
| 15 |
("<a href="license.html">LGPL</a>") |
|---|
| 16 |
has been adopted to govern the use and distribution of |
|---|
| 17 |
above-mentioned application. |
|---|
| 18 |
However, the <a href="license.html">LGPL</a> |
|---|
| 19 |
uses terminology that is |
|---|
| 20 |
more appropriate for a program written in C than one written in |
|---|
| 21 |
Lisp. |
|---|
| 22 |
Nevertheless, |
|---|
| 23 |
the <a href="license.html">LGPL</a> |
|---|
| 24 |
can still be applied to a Lisp program if |
|---|
| 25 |
certain clarifications are made. This document details those |
|---|
| 26 |
clarifications. Accordingly, the license for the open-source Lisp |
|---|
| 27 |
applications consists of this document plus |
|---|
| 28 |
the <a href="license.html">LGPL</a>. |
|---|
| 29 |
Wherever there is a |
|---|
| 30 |
conflict between this document and |
|---|
| 31 |
the <a href="license.html">LGPL</a>, |
|---|
| 32 |
this document takes |
|---|
| 33 |
precedence over |
|---|
| 34 |
the <a href="license.html">LGPL</a>. |
|---|
| 35 |
</p> |
|---|
| 36 |
<p> |
|---|
| 37 |
A "Library" in Lisp is a collection of Lisp functions, data and |
|---|
| 38 |
foreign modules. The form of the Library can be Lisp source code (for |
|---|
| 39 |
processing by an interpreter) or object code (usually the result of |
|---|
| 40 |
compilation of source code or built with some other |
|---|
| 41 |
mechanisms). Foreign modules are object code in a form that can be |
|---|
| 42 |
linked into a Lisp executable. When we speak of functions we do so in |
|---|
| 43 |
the most general way to include, in addition, methods and unnamed |
|---|
| 44 |
functions. Lisp "data" is also a general term that includes the data |
|---|
| 45 |
structures resulting from defining Lisp classes. A Lisp application |
|---|
| 46 |
may include the same set of Lisp objects as does a Library, but this |
|---|
| 47 |
does not mean that the application is necessarily a "work based on the |
|---|
| 48 |
Library" it contains. |
|---|
| 49 |
</p> |
|---|
| 50 |
<p> |
|---|
| 51 |
The Library consists of everything in the distribution file set before |
|---|
| 52 |
any modifications are made to the files. If any of the functions or |
|---|
| 53 |
classes in the Library are redefined in other files, then those |
|---|
| 54 |
redefinitions ARE considered a work based on the Library. If |
|---|
| 55 |
additional methods are added to generic functions in the Library, |
|---|
| 56 |
those additional methods are NOT considered a work based on the |
|---|
| 57 |
Library. If Library classes are subclassed, these subclasses are NOT |
|---|
| 58 |
considered a work based on the Library. If the Library is modified to |
|---|
| 59 |
explicitly call other functions that are neither part of Lisp itself |
|---|
| 60 |
nor an available add-on module to Lisp, then the functions called by |
|---|
| 61 |
the modified Library ARE considered a work based on the Library. The |
|---|
| 62 |
goal is to ensure that the Library will compile and run without |
|---|
| 63 |
getting undefined function errors. |
|---|
| 64 |
</p> |
|---|
| 65 |
<p> |
|---|
| 66 |
It is permitted to add proprietary source code to the Library, but it |
|---|
| 67 |
must be done in a way such that the Library will still run without |
|---|
| 68 |
that proprietary code present. Section 5 of the |
|---|
| 69 |
<a href="license.html">LGPL</a> |
|---|
| 70 |
distinguishes |
|---|
| 71 |
between the case of a library being dynamically linked at runtime and |
|---|
| 72 |
one being statically linked at build time. |
|---|
| 73 |
Section 5 of the |
|---|
| 74 |
<a href="license.html">LGPL</a> |
|---|
| 75 |
states that the former results in an executable that is a "work that |
|---|
| 76 |
uses the Library." |
|---|
| 77 |
Section 5 of the |
|---|
| 78 |
<a href="license.html">LGPL</a> |
|---|
| 79 |
states that the latter |
|---|
| 80 |
results in one that is a "derivative of the Library", which is |
|---|
| 81 |
therefore covered by |
|---|
| 82 |
the <a href="license.html">LGPL</a>. |
|---|
| 83 |
Since Lisp only offers one choice, which is |
|---|
| 84 |
to link the Library into an executable at build time, we declare that, |
|---|
| 85 |
for the purpose applying |
|---|
| 86 |
the <a href="license.html">LGPL</a> |
|---|
| 87 |
to the Library, |
|---|
| 88 |
an executable that results from linking a "work that uses the Library" |
|---|
| 89 |
with the Library |
|---|
| 90 |
is considered a "work that uses the Library" and is therefore NOT |
|---|
| 91 |
covered by the <a href="license.html">LGPL</a>. |
|---|
| 92 |
</p> |
|---|
| 93 |
<p> |
|---|
| 94 |
Because of this declaration, |
|---|
| 95 |
section 6 of |
|---|
| 96 |
<a href="license.html">LGPL</a> |
|---|
| 97 |
is not applicable to |
|---|
| 98 |
the Library. |
|---|
| 99 |
However, in connection with each distribution of this |
|---|
| 100 |
executable, you must also deliver, in accordance with the terms and |
|---|
| 101 |
conditions of the |
|---|
| 102 |
<a href="license.html">LGPL</a>, |
|---|
| 103 |
the source code of Library (or your derivative thereof) |
|---|
| 104 |
that is incorporated into this executable. |
|---|
| 105 |
</p> |
|---|
| 106 |
|
|---|
| 107 |
<p> |
|---|
| 108 |
<u>End of Document</u> |
|---|
| 109 |
</p> |
|---|
| 110 |
|
|---|
| 111 |
</body> |
|---|
| 112 |
|
|---|
| 113 |
</html> |
|---|
