Bug#737901: libv4l-0: Please clarify license of the library.

2014-02-07 Thread Gregor Jasny
Hi Kurt,

On 06/02/14 21:48, Kurt Roeckx wrote:
 According to the copyright file, there are sources covered by the
 GPL-2, GPL-2+, LGPL-2+ and LGPL-2.1+, an some other licenses.  However
 it's not clear which files end up in the resulting library and so
 what the resulting license is, or those from other binaries.
 
 I know that at least some people stay away because of the GPL
 instead of the LGPL.
 
 Could you please clarify the license as they apply to the
 binaries?  And if the GPL applies to the library, could you
 please ask for a change in license so that everything is
 LGPL?

the libv4l libraries (libv4l1, libv4l2, and libv4lconvert are all
covered by LGPL-2.1+). libv4lconvert utilizes two GPL helper binaries to
decode ancient OV51* picture formats. We tried to contact the original
author of this code but got no response.

I will write a paragraph about the licensing of the components on top of
the copyright file.

Thanks,
Gregor


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#737901: libv4l-0: Please clarify license of the library.

2014-02-06 Thread Kurt Roeckx
Package: libv4l-0
Version: 1.0.1-1


Hi,

According to the copyright file, there are sources covered by the
GPL-2, GPL-2+, LGPL-2+ and LGPL-2.1+, an some other licenses.  However
it's not clear which files end up in the resulting library and so
what the resulting license is, or those from other binaries.

I know that at least some people stay away because of the GPL
instead of the LGPL.

Could you please clarify the license as they apply to the
binaries?  And if the GPL applies to the library, could you
please ask for a change in license so that everything is
LGPL?


Kurt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org