Bug#694257: fdk-aac: who knows more?

[Carlos Alberto Lopez Perez]

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?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20130510/47d3f69c/attachment.pgp>