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

[Arto Jantunen]

Carlos Alberto Lopez Perez <clopez at igalia.com> writes:

> 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?

No, not as far as I understand this case. I haven't read through all of
the info, but as I see it this is about either avconv linking against
the GPL-incompatible fdk-aac or libav itself linking against it.

Neither of these options is ok since both libav and avconv are GPL
licensed. The difference between LGPL and GPL only matters in the other
direction, so even if libav was fully LGPL licensed, it could not link
against fdk-aac (due to the previously mentioned "no further
restrictions" clause in both GPL and LGPL).

-- 
Arto Jantunen