From 935ccbddcf97ead5e56cb7d8852a6efa5d94ca42 Mon Sep 17 00:00:00 2001 From: Utz-Uwe Haus Date: Fri, 28 May 2010 15:34:20 +0200 Subject: [PATCH] Clarify licensing issues Signed-off-by: Utz-Uwe Haus --- .gitignore | 3 + LICENSE.LGPL.txt | 165 ++++++++++++++++++++++++++++++++++++++++++++++ LICENSE.Lisp-LGPL-Preface | 58 ++++++++++++++++ README | 14 ++++ 4 files changed, 240 insertions(+) create mode 100644 LICENSE.LGPL.txt create mode 100644 LICENSE.Lisp-LGPL-Preface create mode 100644 README diff --git a/.gitignore b/.gitignore index 07f0bf3..fb20010 100644 --- a/.gitignore +++ b/.gitignore @@ -6,3 +6,6 @@ *.fasl # autogenerated: cuddapi.lisp +distr/include/*.h +distr/include/*.hh +distr/nanotrav/nanotrav diff --git a/LICENSE.LGPL.txt b/LICENSE.LGPL.txt new file mode 100644 index 0000000..65c5ca8 --- /dev/null +++ b/LICENSE.LGPL.txt @@ -0,0 +1,165 @@ + GNU LESSER GENERAL PUBLIC LICENSE + Version 3, 29 June 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + + This version of the GNU Lesser General Public License incorporates +the terms and conditions of version 3 of the GNU General Public +License, supplemented by the additional permissions listed below. + + 0. Additional Definitions. + + As used herein, "this License" refers to version 3 of the GNU Lesser +General Public License, and the "GNU GPL" refers to version 3 of the GNU +General Public License. + + "The Library" refers to a covered work governed by this License, +other than an Application or a Combined Work as defined below. + + An "Application" is any work that makes use of an interface provided +by the Library, but which is not otherwise based on the Library. +Defining a subclass of a class defined by the Library is deemed a mode +of using an interface provided by the Library. + + A "Combined Work" is a work produced by combining or linking an +Application with the Library. The particular version of the Library +with which the Combined Work was made is also called the "Linked +Version". + + The "Minimal Corresponding Source" for a Combined Work means the +Corresponding Source for the Combined Work, excluding any source code +for portions of the Combined Work that, considered in isolation, are +based on the Application, and not on the Linked Version. + + The "Corresponding Application Code" for a Combined Work means the +object code and/or source code for the Application, including any data +and utility programs needed for reproducing the Combined Work from the +Application, but excluding the System Libraries of the Combined Work. + + 1. Exception to Section 3 of the GNU GPL. + + You may convey a covered work under sections 3 and 4 of this License +without being bound by section 3 of the GNU GPL. + + 2. Conveying Modified Versions. + + If you modify a copy of the Library, and, in your modifications, a +facility refers to a function or data to be supplied by an Application +that uses the facility (other than as an argument passed when the +facility is invoked), then you may convey a copy of the modified +version: + + a) under this License, provided that you make a good faith effort to + ensure that, in the event an Application does not supply the + function or data, the facility still operates, and performs + whatever part of its purpose remains meaningful, or + + b) under the GNU GPL, with none of the additional permissions of + this License applicable to that copy. + + 3. Object Code Incorporating Material from Library Header Files. + + The object code form of an Application may incorporate material from +a header file that is part of the Library. You may convey such object +code under terms of your choice, provided that, if the incorporated +material is not limited to numerical parameters, data structure +layouts and accessors, or small macros, inline functions and templates +(ten or fewer lines in length), you do both of the following: + + a) Give prominent notice with each copy of the object code that the + Library is used in it and that the Library and its use are + covered by this License. + + b) Accompany the object code with a copy of the GNU GPL and this license + document. + + 4. Combined Works. + + You may convey a Combined Work under terms of your choice that, +taken together, effectively do not restrict modification of the +portions of the Library contained in the Combined Work and reverse +engineering for debugging such modifications, if you also do each of +the following: + + a) Give prominent notice with each copy of the Combined Work that + the Library is used in it and that the Library and its use are + covered by this License. + + b) Accompany the Combined Work with a copy of the GNU GPL and this license + document. + + c) For a Combined Work that displays copyright notices during + execution, include the copyright notice for the Library among + these notices, as well as a reference directing the user to the + copies of the GNU GPL and this license document. + + d) Do one of the following: + + 0) Convey the Minimal Corresponding Source under the terms of this + License, and the Corresponding Application Code in a form + suitable for, and under terms that permit, the user to + recombine or relink the Application with a modified version of + the Linked Version to produce a modified Combined Work, in the + manner specified by section 6 of the GNU GPL for conveying + Corresponding Source. + + 1) Use a suitable shared library mechanism for linking with the + Library. A suitable mechanism is one that (a) uses at run time + a copy of the Library already present on the user's computer + system, and (b) will operate properly with a modified version + of the Library that is interface-compatible with the Linked + Version. + + e) Provide Installation Information, but only if you would otherwise + be required to provide such information under section 6 of the + GNU GPL, and only to the extent that such information is + necessary to install and execute a modified version of the + Combined Work produced by recombining or relinking the + Application with a modified version of the Linked Version. (If + you use option 4d0, the Installation Information must accompany + the Minimal Corresponding Source and Corresponding Application + Code. If you use option 4d1, you must provide the Installation + Information in the manner specified by section 6 of the GNU GPL + for conveying Corresponding Source.) + + 5. Combined Libraries. + + You may place library facilities that are a work based on the +Library side by side in a single library together with other library +facilities that are not Applications and are not covered by this +License, and convey such a combined library under terms of your +choice, if you do both of the following: + + a) Accompany the combined library with a copy of the same work based + on the Library, uncombined with any other library facilities, + conveyed under the terms of this License. + + b) Give prominent notice with the combined library that part of it + is a work based on the Library, and explaining where to find the + accompanying uncombined form of the same work. + + 6. Revised Versions of the GNU Lesser General Public License. + + The Free Software Foundation may publish revised and/or new versions +of the GNU Lesser General Public License from time to time. Such new +versions will be similar in spirit to the present version, but may +differ in detail to address new problems or concerns. + + Each version is given a distinguishing version number. If the +Library as you received it specifies that a certain numbered version +of the GNU Lesser General Public License "or any later version" +applies to it, you have the option of following the terms and +conditions either of that published version or of any later version +published by the Free Software Foundation. If the Library as you +received it does not specify a version number of the GNU Lesser +General Public License, you may choose any version of the GNU Lesser +General Public License ever published by the Free Software Foundation. + + If the Library as you received it specifies that a proxy can decide +whether future versions of the GNU Lesser General Public License shall +apply, that proxy's public statement of acceptance of any version is +permanent authorization for you to choose that version for the +Library. diff --git a/LICENSE.Lisp-LGPL-Preface b/LICENSE.Lisp-LGPL-Preface new file mode 100644 index 0000000..5a94e0b --- /dev/null +++ b/LICENSE.Lisp-LGPL-Preface @@ -0,0 +1,58 @@ +Copyright (C) 2009-2010 by Utz-Uwe Haus + +This code is free software; you can redistribute it and/or modify it +under the terms of the version 3 of the GNU Lesser General Public License +(GPL) found in the file LICENSE.LGPL published by the Free Software +Foundation, as clarified by Franz Inc.'s preamble to the LGPL found in +: + +Preamble to the Gnu General Public License +------------------------------------------ + +Copyright (c) 2000 Franz Incorporated, Berkeley, CA 94704 + +The concept of the GNU Lesser General Public License version 2.1 ("LGPL") has +been adopted to govern the use and distribution of above-mentioned application. +However, the LGPL uses terminology that is more appropriate for a program +written in C than one written in Lisp. Nevertheless, the LGPL can still be +applied to a Lisp program if certain clarifications are made. This document +details those clarifications. Accordingly, the license for the open-source Lisp +applications consists of this document plus the LGPL. Wherever there is a +conflict between this document and the LGPL, this document takes precedence +over the LGPL. + +A "Library" in Lisp is a collection of Lisp functions, data and foreign modules. The form of the Library can be Lisp source code (for processing by an interpreter) or object code (usually the result of compilation of source code or built with some other mechanisms). Foreign modules are object code in a form that can be linked into a Lisp executable. When we speak of functions we do so in the most general way to include, in addition, methods and unnamed functions. Lisp "data" is also a general term that includes the data structures resulting from defining Lisp classes. A Lisp application may include the same set of Lisp objects as does a Library, but this does not mean that the application is necessarily a "work based on the Library" it contains. + +The Library consists of everything in the distribution file set before any +modifications are made to the files. If any of the functions or classes in the +Library are redefined in other files, then those redefinitions ARE considered a +work based on the Library. If additional methods are added to generic functions +in the Library, those additional methods are NOT considered a work based on the +Library. If Library classes are subclassed, these subclasses are NOT considered +a work based on the Library. If the Library is modified to explicitly call +other functions that are neither part of Lisp itself nor an available add-on +module to Lisp, then the functions called by the modified Library ARE +considered a work based on the Library. The goal is to ensure that the Library +will compile and run without getting undefined function errors. + +It is permitted to add proprietary source code to the Library, but it must be +done in a way such that the Library will still run without that proprietary +code present. Section 5 of the LGPL distinguishes between the case of a library +being dynamically linked at runtime and one being statically linked at build +time. Section 5 of the LGPL states that the former results in an executable +that is a "work that uses the Library." Section 5 of the LGPL states that the +latter results in one that is a "derivative of the Library", which is therefore +covered by the LGPL. Since Lisp only offers one choice, which is to link the +Library into an executable at build time, we declare that, for the purpose +applying the LGPL to the Library, an executable that results from linking a +"work that uses the Library" with the Library is considered a "work that uses +the Library" and is therefore NOT covered by the LGPL. + +Because of this declaration, section 6 of LGPL is not applicable to the +Library. However, in connection with each distribution of this executable, you +must also deliver, in accordance with the terms and conditions of the LGPL, the +source code of Library (or your derivative thereof) that is incorporated into +this executable. + +End of Document + diff --git a/README b/README new file mode 100644 index 0000000..9b8ef43 --- /dev/null +++ b/README @@ -0,0 +1,14 @@ +This is a swig/cffi wrapper around University of Colorado at Boulder's CUDD +library. It is a work-in-progress, but works for me with Allegro CL and SBCL +on linux/intel 32bit and 64bit. + +The wrapper code is released under the Lisp Lesser GPL, see +. + +A complete distribution of cudd-2.4.2 is enclosed in the distr/ subdirectory +for convenience. See distr/LICENSE for the cudd license. + +Utz-Uwe Haus + +Fri May 28 15:25:10 CEST 2010 + -- 2.11.4.GIT