[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#435070: Package contains other copyright than GPL



On Sun, 29 Jul 2007 11:40:32 +0530
"Kartik Mistry" <kartik.mistry@gmail.com> wrote:

> Package: deb-gview
> Version: 0.1.2
> Severity: important
> Tags: patch
> 
> While viewing debian/copyright of deb-gview (using deb-gview), I found
> that it has only GPL listed in copyright file.

Correct.

> But, since package is using install-sh, it should have listed
> copyright/license of it in debian/copyright.

If that was true, you would need to file thousands of bugs for all the
other autotools packages that use install-sh via automake. The file is
actually copied from a symlink during the packaging process:

lrwxrwxrwx 34 2007-05-23 00:00 install-sh -> /usr/share/automake-1.9/install-sh

You would also need to require that ALL LGPL packages using automake
would have to be licensed under the GPL because, by this measure, they
include GPL code. Somehow, I don't think that will stick. e.g.
libgpewidget and probably libglib2.0-0 and libgtk+2.0-0 as well.

The deb-gview CVS does not contain the file:
http://alioth.debian.org/plugins/scmcvs/cvsweb.php/dpkg-view/?cvsroot=dpkg-view

CC'ing devel to clarify.

I use the same build method for libqof1, pilot-qof, gpe-expenses. It is
also used in other GPE packages and other automake/autotools based
packages that I have worked on elsewhere. In every case, install-sh is
unchanged from the automake file.

I don't see that it makes sense to carry copyright information into
every single package that uses automake in this way. 

The script isn't compiled into the program, it doesn't form part of the
distributed binaries, it is part of the build system - much like gcc or
dpkg or bash or automake itself. The only difference is that this
script needs to exist within the source directory - if anything, that
could be considered a bug in automake, maybe the script should actually
be able to run from /usr/bin. True, you cannot (currently) build the
package without install-sh but then you can't build it without
automake, autoconf or dpkg either.

It could also be considered as an automake bug that the 'make dist'
target requires install-sh to be copied into the .orig.tar.gz when it
could (presumably) just as easily be copied into place when automake is
first run during the build itself.

-- 


Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/

Attachment: pgpAhD4Iuxlqj.pgp
Description: PGP signature


Reply to: