Quoting Carlos Alberto Lopez Perez (2013-05-10 13:28:20) > On 10/05/13 07:41, Arto Jantunen wrote: > > The difference between the GPL and the LGPL does solve the problem > > if the program you are developing wants to link to both LGPL > > licensed and GPL incompatible libraries, assuming that the license > > of the program itself is not either GPL or LGPL. Parts of libav are > > GPL and the rest is LGPL, thus the problem remains. > > So the problem all boils down that the fact that libav contains GPL > code? > > I was supposing that libav was 100% LGPL (with no GPL code). If libav > contains GPL code then the whole viral nature of the GPL license will > entangle everything. AFAIK there is no practical difference between > being libav 100% GPL or beeing libav 1% GPL. You have to obey the GPL > in both cases, which means that you can't link libav with > GPL-incompatible license software. > > Isn't it?
Please read the section "License of the Debian ffmpeg packages" of /usr/share/doc/libav-tools/README.Debian.gz and ask if afterwards these matters are is still uncertain. The very purpose of that text is to clarify situations like this, I believe. So we should promote that text whenever such issue comes up, and improve it if not clear enough. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130510160311.18273.2...@bastian.jones.dk
