Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: ASDF
Upstream-Contact: asdf-devel@common-lisp.net
Source: https://common-lisp.net/project/asdf/

Files: *
Copyright: 2001-2019 Daniel Barlow, Francois-Rene Rideau, Robert P. Goldman, and contributors
Comment: This is the MIT license, but Debian, after GNU, calls it the Expat license
 to unambiguously distinguish it from other licenses once used by MIT.
License: Expat
 (This is the MIT / X Consortium license as taken from
  http://www.opensource.org/licenses/mit-license.html on or about
  Monday; July 13, 2009)
 .
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the
 "Software"), to deal in the Software without restriction, including
 without limitation the rights to use, copy, modify, merge, publish,
 distribute, sublicense, and/or sell copies of the Software, and to
 permit persons to whom the Software is furnished to do so, subject to
 the following conditions:
 .
 The above copyright notice and this permission notice shall be
 included in all copies or substantial portions of the Software.
 .
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
 MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
 NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
 LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
 OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
 WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Files: contrib/fiveam-asdf/*
Copyright: 2012-2018 Smart Information Flow Technologies, d/b/a SIFT, LLC and Robert P. Goldman
License: LLGPL
 Preamble to the Gnu Lesser 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.
 .
 On Debian systems, the complete text of version 2.1 of the Lesser GNU General
 Public License can be found in '/usr/share/common-licenses/LGPL-2.1'.

Files: debian/*
Copyright: 2002 Kevin M. Rosenberg <kmr@debian.org>
License: GPL-2
 On Debian systems, the full text of the GNU GPL v2 can be found in the file
 `/usr/share/common-licenses/GPL-2'.
Comment: This package was initially debianized by Kevin M. Rosenberg <kmr@debian.org>
 on Fri, 16 Aug 2002 23:14:49 -0600.
 Peter Van Eynde took over in 2005. Then from 2010 to 2014, Francois-Rene Rideau
 maintained the debian package as part of the upstream git repository.
