You can clone with
Cannot retrieve contributors at this time
Prequel to the Gnu Lesser General Public LicenseCopyright (c) 2000 Franz Inc., Berkeley, CA 94704Franz Inc. has adopted the concept of the GNU Lesser General PublicLicense version 2.1 ("LGPL") to govern the use and distribution ofAllegroServe. However, LGPL uses terminology that is more appropriatefor a program written in C than one written in Lisp. Nevertheless,LGPL can still be applied to a Lisp program if certain clarificationsare made. This document details those clarifications.Accordingly, the license for AllegroServe consists of this documentplus LGPL. Wherever there is a conflict between this document andLGPL, this document takes precedence over LGPL.A "Library" in Lisp is a collection of Lisp functions, data andforeign modules. The form of the Library can be Lisp source code (forprocessing by an interpreter) or object code (usually the result ofcompilation of source code or built with some othermechanisms). Foreign modules are object code in a form that can belinked into a Lisp executable. When we speak of functions we do so inthe most general way to include, in addition, methods and unnamedfunctions. Lisp "data" is also a general term that includes the datastructures resulting from defining Lisp classes.A Lisp application may include the same set of Lisp objects as does aLibrary, but this does not mean that the application is necessarily a"work based on the Library" it contains.The AllegroServe Library consists of everything in the AllegroServedistribution file set before any modifications are made to the files.If any of the functions or classes in the AllegroServe Library areredefined in other files, then those redefinitions ARE considered awork based on the AllegroServe Library. If additional methods areadded to generic functions in the AllegroServe Library, thoseadditional methods are NOT considered a work based on the AllegroServeLibrary. If AllegroServe classes are subclassed, these subclasses areNOT considered a work based on the AllegroServe Library. If theAllegroServe Library is modified to explicitly call other functionsthat are neither part of Lisp itself nor an available add-on module toLisp, then the functions called by the modified AllegroServe LibraryARE considered a work based on the AllegroServe Library. The goal isto ensure that the AllegroServe Library will compile and run withoutgetting undefined function errors.It is permitted to add proprietary source code to the AllegroServeLibrary, but it must be done in a way such that the AllegroServeLibrary will still run without that proprietary code present.Section 5 of the LGPL distinguishes between the case of a librarybeing dynamically linked at runtime and one being statically linked atbuild time. Section 5 of the LGPL states that the former results in anexecutable that is a "work that uses the Library." Section 5 of theLGPL states that the latter results in one that is a "derivative ofthe Library", which is therefore covered by LGPL. Since Lisp onlyoffers one choice, which is to link the Library into an executable atbuild time, we declare that, for the purpose applying LGPL to theAllegroServe Library, an executable that results from linking a "workthat uses the AllegroServe Library" with the Library is considered a"work that uses the Library" and is therefore NOT covered by LGPL.Because of this declaration, section 6 of LGPL is not applicable tothe AllegroServe Library. However, in connection with eachdistribution of this executable, you must also deliver, in accordancewith the terms and conditions of the LGPL, the source code ofAllegroServe Library (or your derivative thereof) that is incorporatedinto this executable.