d-m.o dependency tree

[Alessio Treglia]

On Fri, Feb 10, 2012 at 9:19 AM, Fabian Greffrath <fabian at greffrath.com> wrote:
> For the initial upload to Debian we could simply configure --without-mp4v2.
> BTW, the library is not affected, only the CLI frontend. I assume it will be
> OK to ship both sources in the same tarball as long as they are not linked
> together?
>
> OTOH, I am still not sure what happens when you link GPL and MPL code. I
> have read <http://www.gnu.org/licenses/license-list.en.html#MPL-2.0> but did
> not understand a word. :/

Regarding MPL-2.0, gnu.org explicitly states [1]: "This is a free
software license. Section 3.3 provides indirect compatibility between
this license and the GNU GPL version 2.0, the GNU LGPL version 2.1,
the GNU AGPL version 3.0, and all later versions of those licenses.
[...]"

And regarding MPL-1.1, it says [2]: "This is a free software license
which is not a strong copyleft; unlike the X11 license, it has some
complex restrictions that make it incompatible with the GNU GPL. That
is, a module covered by the GPL and a module covered by the MPL cannot
legally be linked together. We urge you not to use the MPL for this
reason. [...]"

So, if the faac's CLI frontend links against mp4v2 yes, it is affected
by a serious issue and we must disable the offending linking flag.
Otherwise, no, it isn't.

www.gnu.org's website is often extremely useful for searching
information about compatibility between GNU's licenses and
the-rest-of-the-world.

[1] http://www.gnu.org/licenses/license-list.en.html#MPL
[2] http://www.gnu.org/licenses/license-list.en.html#MPL-2.0

-- 
Alessio Treglia          | www.alessiotreglia.com
Debian Developer         | alessio at debian.org
Ubuntu Core Developer    | quadrispro at ubuntu.com
0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A