I've completely reformatted the debian copyright file (using the new
machine readable format) and done some grepping for rogue files. I've
attached a copy and I think this identified all the non-LGPL files (
parts of files) apart from the additional libraries shipped in lib
(which I also need to deal with and have an outstanding bug report).
This list might be useful more generally. It would be great if we
could tidy up the odd license files for consistency. In particular
whether examples are GPL or LGPL is a bit random.
Andrew
On Wed, Sep 17, 2014 at 11:47:30PM -0700, Alan Irwin wrote:
> On 2014-09-17 23:57+0100 Andrew Ross wrote:
>
> >
> > Alan,
> >
> > My reading of the bug report was different to yours. There are a
> > number of files (e.g. examples which contain licenses different to
> > the LGPL. The debian/copyright file is supposed to contain mention
> > of ALL licenses which are applied to any part of the software. Some
> > (but not all) of the examples are GPL rather than LGPL.
>
> Hmm. That is true but that issue should be easy to fix, by using
> the following find command:
>
> software@raven> find . -type f |grep -v .git \
> |xargs grep -li copyright| xargs grep -Li "public license" |wc -l
> 109
>
> So there are 109 such files but presumably some of them are
> false positives, and when you replace "wc -l" by
> "xargs grep -i copyright -A20" (or whatever command seems reasonable
> to you), you will be able to figure out which of those 109 should be
> mentioned in Copyright.
>
> However, I think you should also on general grounds include wording in
> Copyright specifically stating all files in the source code have the
> exact LGPL license terms in that file except for a list of exceptions
> that you (in the ~109 above) and I (assuming I switch from the current
> default LGPL to the specific openBSD documentation license for the
> doxygen-generated files) do need to refine.
>
> His report did specifically mentioned some doxygen-generated files
> that had some non-lgpl copyright info in them . But this is strong
> evidence of his complete misunderstanding of doxygen-generated files.
> Roughly a third of those are source listings in html form, and they
> necessarily include all the source text (i.e., from some of the 109
> above) and therefore mention all the copyright notices for that source
> code. But that obviously has nothing to do with the actual generated
> file copyright which is a completely different matter!
>
> Look up the list of his bug reports. There are all similar to the one
> for PLplot so I think he has put together a script that blindly looks
> for all source code files that have the copyright word in them, and
> then files rather unintelligent reports (at least in the
> doxygen-generated case) about copyright inconsistencies he finds for
> those files. So my semi-facetious guess is he will claim when I use
> the openBSD copyright text for doxygen-generated files even more
> copyright "inconsistencies" because those files (when reporting
> source) will have LGPL text in them as well as that openBSD
> documentation text. At which point, he will have convincingly
> demonstrated he does not know the difference between documentation
> license and the license for the code quoted by that documentation. At
> which point, his "bug report" for PLplot should be declared spam. :-)
>
> Alan
> __________________________
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Plplot-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/plplot-devel
Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: plplot
Source: http://sf.net/plplot/
Upstream source has been repackaged to remove generated files which
are non-DFSG compliant.
License: LGPL-2+
Comment: Unless otherwise stated all files are released under the LGPL-2+.
Any file that has a explicit copyright notice may be distributed
under the terms of both the LGPL and whatever stated conditions accompany
the copyright.
Files: *
Copyright: 1998-2004 Joao Cardoso
1998-1999, 2001, 2002, 2004 Vince Darley
1991-2002 Geoffrey Furnish
1999-2014 Alan W. Irwin
1998-2005 Rafael Laboissiere
1991-2005 Maurice LeBrun
2004-2014 Arjen Markus
2004 Andrew Roach
2002 David Schleef
2004-2014 Andrew Ross
2004, 2005 Thomas J. Duck
Licence: LGPL-2+
Comment: The intent behind distributing PLplot under the LGPL is to ensure that
it
continues to evolve in a positive way, while remaining freely
distributable. The package is considered a "library" even though there
are associated programs, such as plrender, pltek, plserver, and pltcl.
The ties between these programs and the library are so great that I
consider them as part of the library, so distribution under the terms of
the LGPL makes sense. Software developers are allowed and encouraged to
use PLplot as an integral part of their product, even a commercial
product. Under the conditions of the LGPL, however, the PLplot source
code must remain freely available, including any modifications you make to
it (if you distribute a program based on the modified library). Please
read the full license for more info.
Files: bindings/octave/PLplot/toggle_plplot_use.m
examples/octave/x0[1-9]c.m
examples/octave/x1[0-9]c.m
examples/octave/x22c.m
example/octave/p*.m
Copyright: 1998-2003 Joao Cardodo
2004-2006,2008 Andrew Ross
2004 Rafael Laboissiere
License: GPL-2+
Comment: The octave front end which links to the PLplot library (but not
vice versa), and which is otherwise independent of PLplot is copyright
under the GPL license (see COPYING).
Files: examples/ada/x23a.adb
examples/ada/xthick23a.adb
c/plplotcanvas_*.c
c++/qt*
python/plplotcanvas_*.py
Copyright: 2004, 2005 Thomas Duck
2009 Imperial College, London
2005 Stephen Leake
2008 Jerry Bauck
License: GPL-2+
Files: utils/plrender.c
src/plargs.c
Copyright:
License: MIT
Copyright: 1987, 1988 by Digital Equipment Corporation, Maynard, Massachusetts,
and the Massachusetts Institute of Technology, Cambridge, Massachusetts.
Comment: The startup code used in argument handling in these files
is partially derived from "xterm.c" of the X11R5 distribution.
Files: doc/docbook/*
Copyright: 1994 Geoffrey Furnish and Maurice LeBrun
1999-2013 Alan W. Irwin
1999, 2000, 2001, 2002, 2003, 2004 Rafael Laboissiere
2003 Joao Cardoso
2004, 2007 Andrew Ross
2004 Andrew Roach
2008-2010 Jerry Bauck
2008-2009 Hezekiah M. Carty
2007 Hazen Babcock
2005 Thomas Duck
License: plplot-doc
Files: data/*.shp
data/*.shx
License: public-domain
Comment: The shapefiles (.shx and .shp files) supplied with PLplot are
in the public domain. The data is downloaded from the free resource
Natural Earth (www.naturalearthdata.com).
Files: bindings/f95/plstubs.h
bindings/tk-x-plat/Memberscope.tcl
License: public-domain
Comment: These files are explicitly marked as being released in the public
domain
License: LGPL-2+
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public
License as published by the Free Software Foundation; either
version 2 of the License, or (at your option) any later version.
.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Library General Public License for more details.
.
You should have received a copy of the GNU Library General Public
License along with this library; if not, write to the Free Software
Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
.
On Debian systems, the full text of the GNU Library General Public
License version 2 can be found in the file
`/usr/share/common-licenses/LGPL-2'.
License: GPL-2+
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.
.
This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.
.
On Debian systems, the full text of the GNU General Public License
version 2 can be found in the file `/usr/share/common-licenses/GPL-2'.
License: MIT
******************************************************************************
Copyright 1987, 1988 by Digital Equipment Corporation, Maynard, Massachusetts,
and the Massachusetts Institute of Technology, Cambridge, Massachusetts.
.
All Rights Reserved
.
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and that
both that copyright notice and this permission notice appear in
supporting documentation, and that the names of Digital or MIT not be
used in advertising or publicity pertaining to distribution of the
software without specific, written prior permission.
.
DIGITAL DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING
ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL
DIGITAL BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR
ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,
ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
SOFTWARE.
******************************************************************************
License: plplot-doc
The documentation files are distributed under the following license terms:
===========================================================================
.
Redistribution and use in source (XML DocBook) and "compiled" forms
(HTML, PDF, PostScript, DVI, TeXinfo and so forth) with or without
modification, are permitted provided that the following conditions are
met:
.
1. Redistributions of source code (XML DocBook) must retain the
above copyright notice, this list of conditions and the following
disclaimer as the first lines of this file unmodified.
.
2. Redistributions in compiled form (transformed to other DTDs,
converted to HTML, PDF, PostScript, and other formats) must
reproduce the above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or other
materials provided with the distribution.
.
Important: THIS DOCUMENTATION IS PROVIDED BY THE PLPLOT PROJECT "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PLPLOT PROJECT BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENTATION,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.
===========================================================================
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Plplot-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plplot-devel
