Qt/Embedded
David Johnson
david at usermode.org
Mon Nov 13 07:53:23 UTC 2000
On Sunday 12 November 2000 11:07 pm, kmself at ix.netcom.com wrote:
> > Will a BSD or MIT application even be able to use these #ifdefs so
> > that the end user can recompile in private?
>
> Oblig: IANAL
>
> It's generally accepted that the MIT license is convertible to GPL, as
> is BSD without advertising clause. Programs licensed under such terms
> might be considered GPLd if linked to the Qt libraries.
I understood it to be in the opposite direction. The GPL apparently considers
dynamic linkage to be derivation of the copyrighted work, but derivation
has a definite direction.
A GPL application could link to or incorporate BSD/MIT code, but that BSD/MIT
code could not link to or incorporate GPL code. Under section 2 of the GPL it
seems to be okay as it is the distribution of the whole that must be under
the GPL, not the individual "independent and separate works". However,
section 3 says that all source code must be distribute under the terms of
section 1, which says "publish on each copy an appropriate copyright notice"
and "give any other recipients of the Program a copy of this License".
This is kind of confusing, as section 1 pertains only to the original work
(verbatim copies), while section 2 pertains to derivative or collective
works. So does section 3 mean to apply section 1 OR section 2 as appropriate,
or is it saying that section 1 AND section 2 be applied to all parts
regardless of whether they are original, derivative or collective?
> Mozilla is going to be released under a dual or multi-license scheme,
> including the GNU GPL, and possibly the GNU LGPL, as well as the MozPL
> and some legacy NPL code (last I'd heard, NPL was being strongly
> deprecated in favor of MozPL). There's an announcement of same at
> http://www.mozilla.org/.
Can a dual-licensed work be linked to GPL code if one of the licenses is not
compatible with the GPL? This would be a pretty big loophole.
--
David Johnson
___________________
http://www.usermode.org
More information about the License-discuss
mailing list