On Thu, 10 Jan 2013 09:55:12 +0100 Reinhard Tartler wrote: [...] > Oh I'm sorry, I mixed that up. There is no clear answer on that > because it depends. Most of the files are LGPL, but some hand-written > assembler optimizations are GPL-2+. The configure script offers an > --enable-gpl switch that includes those GPL-2+ sources. We do enable > this switch for all packages we produce in Debian. > > In theory, we could probably also provide an LGPL build of libavcodec. > Fortunately, nobody has requested that so far.
Wait, are you saying that those few GPL-licensed files: [...] | Files: libavdevice/x11grab.c | libavfilter/yadif.h | libavfilter/vf_blackframe.c | libavfilter/vf_boxblur.c | libavfilter/vf_cropdetect.c | libavfilter/vf_delogo.c | libavfilter/vf_hqdn3d.c | libavfilter/vf_yadif.c | libavfilter/x86/yadif.c | libavfilter/x86/yadif_template.c [...] | License: GPL-2+~Libav [...] are compiled into, or linked with, each shared object (*.so) shipped in all Debian binary packages built from the libav source package? In other words, are you saying that all binary packages built from the libav Debian source package are effectively under GPL-2+ (except for libavcodec-extra-* and libav-dbg, which are effectively under GPL-3+)? Isn't there any binary package effectively under LGPL-2.1+? Please clarify, since this may heavily affect the resolution of licensing issues for other packages! -- http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt New GnuPG key, see the transition document! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpm2cLDJNIEU.pgp
Description: PGP signature
