-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: lilypond
Upstream-Contact: lilypond-devel@gnu.org
Source: http://www.lilypond.org/
Files: *
-Copyright: 1993--2015, Han-Wen Nienhuys <hanwen@lilypond.org>
- 1996--2015, Jan Nieuwenhuizen <janneke@gnu.org>
+Copyright: 1993--2017, Han-Wen Nienhuys <hanwen@lilypond.org>
+ 1996--2017, Jan Nieuwenhuizen <janneke@gnu.org>
License: GPL-3+
Files: debian/*
-Copyright: 2009-2014 Don Armstrong <don@debian.org>
+Copyright: 2009-2017 Don Armstrong <don@debian.org>
2005-2008 Thomas Bushnell, BSG <tb@debian.org>
- 2016 Dr. Tobias Quathamer <toddy@debian.org>
+ 2016-2017 Dr. Tobias Quathamer <toddy@debian.org>
1997-2004, 2017 Anthony Fok <foka@debian.org>
License: GPL-2+
Copyright: Han-Wen Nienhuys, Jan Nieuwenhuizen and Graham Percival
License: GFDL-1.3+
-Files: Documentation/snippet
-Copyright: Han-Wen Nienhuys, Jan Nieuwenhuizen and Graham Percival
-License: GFDL-1.3+
-
Files: input/regression/musicxml/*
Copyright: 2008-2010, Reinhold Kainhofer
License: MIT
Files: mf/*
-Copyright: 1996--2015, The LilyPond authors (lilypond.org)
+Copyright: 1996--2017, The LilyPond authors (lilypond.org)
License: OFL-1.1
Comment: with Reserved Font Name "Emmentaler" and "Feta".
Copyright: 2010--2012, Reinhold Kainhofer <reinhold@kainhofer.com>
License: GPL-3+
-Files: lily/out/parser.cc
- lily/out/parser.hh
-Copyright: 1984, 1989-1990, 2000-2006 Free Software Foundation
-License: GPL-2+
-
Files: scripts/lilymidi.py
scripts/lilysong.py
Copyright: 2006--2012, Brailcom, o.p.s
Copyright: 1996-2010 Free Software Foundation, Inc.
License: LGPL-2.1+
-Files: guile18/doc/tutorial
+Files: guile18/doc/tutorial/*
Copyright: 1997, 1998, 2004, 2006 Free Software Foundation
License: Guile-Tutorial
Permission is granted to make and distribute verbatim copies of
.
You may use this license for any work of which you hold the copyright
and which you wish to distribute. This license may be particularly
- suitable if your work is TeX-related (such as a LaTeX package), but
- it is written in such a way that you can use it even if your work is
+ suitable if your work is TeX-related (such as a LaTeX package), but
+ it is written in such a way that you can use it even if your work is
unrelated to TeX.
.
The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE',
. `Derived Work'
Any work that under any applicable law is derived from the Work.
.
- `Modification'
+ `Modification'
Any procedure that produces a Derived Work under any applicable
law -- for example, the production of a file containing an
original file associated with the Work or a significant portion of
no such explicit nomination then it is the `Copyright Holder' under
any applicable law.
.
- `Base Interpreter'
+ `Base Interpreter'
A program or process that is normally needed for running or
- interpreting a part or the whole of the Work.
+ interpreting a part or the whole of the Work.
.
A Base Interpreter may depend on external components but these
are not considered part of the Base Interpreter provided that each
external component clearly identifies itself whenever it is used
interactively. Unless explicitly specified when applying the
license to the Work, the only applicable Base Interpreter is a
- `LaTeX-Format' or in the case of files belonging to the
+ `LaTeX-Format' or in the case of files belonging to the
`LaTeX-format' a program implementing the `TeX language'.
.
.
distribute a Derived Work provided the following conditions are met
for every component of the Work unless that component clearly states
in the copyright notice that it is exempt from that condition. Only
- the Current Maintainer is allowed to add such statements of exemption
- to a component of the Work.
+ the Current Maintainer is allowed to add such statements of exemption
+ to a component of the Work.
.
a. If a component of this Derived Work can be a direct replacement
for a component of the Work when that component is used with the
.
d. You distribute at least one of the following with the Derived Work:
.
- 1. A complete, unmodified copy of the Work;
+ 1. A complete, unmodified copy of the Work;
if your distribution of a modified component is made by
offering access to copy the modified component from a
designated place, then offering equivalent access to copy
to honor the rest of the conditions in this license.
. b. If a Derived Work is distributed under a different license, that
Derived Work must provide sufficient documentation as part of
- itself to allow each recipient of that Derived Work to honor the
+ itself to allow each recipient of that Derived Work to honor the
restrictions in Clause 6 above, concerning changes from the Work.
.
11. This license places no restrictions on works that are unrelated to
.
b. If the Current Maintainer is not reachable and the Copyright
Holder agrees that maintenance of the Work be passed to you,
- then this takes effect immediately upon announcement.
+ then this takes effect immediately upon announcement.
.
4. If you make an `intention announcement' as described in 2b. above
and after three months your intention is challenged neither by
% version 2005/12/01 or later.
%
% This work has the LPPL maintenance status `maintained'.
- %
+ %
% The Current Maintainer of this work is M. Y. Name.
%
% This work consists of the files pig.dtx and pig.ins
`Current Maintainer' referring to the person `M. Y. Name'.
.
If you do not want the Maintenance section of LPPL to apply to your
- Work, change `maintained' above into `author-maintained'.
+ Work, change `maintained' above into `author-maintained'.
However, we recommend that you use `maintained', as the Maintenance
section was added in order to ensure that your Work remains useful to
the community even when you can no longer maintain and support it
impossible for the licensee to determine what is considered by you
to comprise the Work and, in such a case, the licensee would be
entitled to make reasonable conjectures as to which files comprise
- the Work.
+ the Work.
License: MIT
projects / lilypond.git / commitdiff