[haiku-development] Re: INPUT / VOTE : --include-gpl-addons
- From: Anoop Kumar Narayanan <anoop.kn@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sat, 22 Aug 2009 15:44:22 +0530
Sorry about that !
My reply for:
Stefano and Urias
That's the point his addon isn't MIT anymore with GPL code, its GPL.
Moreover, GPL paranoia comes into play only during the time of
redistribution, If GPL code is part of the redistributable, then the
license of the redistributable is should be GPL.
So if you write a hardware driver for windows with GPL license, then
any modifications to the driver by someone else must be made public
under GPL. If windows is redistributed with GPL driver, then windows
becomes GPL. Untill the time windows is distributed with GPL, Windows
is still Closed source. Technically the person writing the driver is
at fault, but nobody sues this chap cause he probably doesn't have a
dime. :)
By introducing GPL code in Third party software, by a fourth party,
then the third party isn't directly affected (as he is not breaking
GPL licensing, its the fourth party that is breaking it by introducing
incompatible license), but should the third party start distributing
his/her product with the fourth party's addon, then the Third party
should open is under the license of GPL.
To summarize, B doesn't have to as B isn't using GPL in his software
or distributing with it. Infact I don't think GPL and (MIT / BSD /
Closed Source) can be mixed together, LGPL can be.
Which is where the core of the Haiku library, should never be GPL.
And, if GPL can be seperated by providing another library it, would
solve all problems. :)
Regards,
-Anoop
On Sat, Aug 22, 2009 at 3:37 PM, Anoop Kumar
Narayanan<anoop.kn@xxxxxxxxx> wrote:
> That's the point his addon isn't MIT anymore with GPL code, its GPL.
> Moreover, GPL paranoia comes into play only during the time of
> redistribution, If GPL code is part of the redistributable, then the
> license of the redistributable is should be GPL.
>
> So if you write a hardware driver for windows with GPL license, then
> any modifications to the driver by someone else must be made public
> under GPL. If windows is redistributed with GPL driver, then windows
> becomes GPL. Untill the time windows is distributed with GPL, Windows
> is still Closed source. Technically the person writing the driver is
> at fault, but nobody sues this chap cause he probably doesn't have a
> dime. :)
>
> By introducing GPL code in Third party software, by a fourth party,
> then the third party isn't directly affected (as he is not breaking
> GPL licensing, its the fourth party that is breaking it by introducing
> incompatible license), but should the third party start distributing
> his/her product with the fourth party's addon, then the Third party
> should open is under the license of GPL.
>
> To summarize, B doesn't have to as B isn't using GPL in his software
> or distributing with it. Infact I don't think GPL and (MIT / BSD /
> Closed Source) can be mixed together, LGPL can be.
>
> Which is where the core of the Haiku library, should never be GPL.
> And, if GPL can be seperated by providing another library it, would
> solve all problems. :)
>
> Regards,
> -Anoop
>
> On Fri, Aug 21, 2009 at 5:49 PM, Stefano
> Ceccherini<stefano.ceccherini@xxxxxxxxx> wrote:
>> 2009/8/21 Stefano Ceccherini <stefano.ceccherini@xxxxxxxxx>:
>>> 2009/8/20 Ingo Weinhold <ingo_weinhold@xxxxxx>:
>>
>>> Sorry but I can't get it.
>>> Consider the following scenario:
>>> - Someone writes a LGPL OS (A), with a LGPL media player, which accepts
>>> addons.
>>> - Someone (else) writes a closed source os (B) with a closed source
>>> media player, which uses the same addon interface as the above media
>>> player, and it's binary compatible to it.
>>
>>> - A third person writes a closed source addon for the LGPL OS using
>>> GPL code, and provide a binary package only for A (and B indirectly)
>>
>> Sorry, this was meant to be:
>>
>> - A third person writes a MIT addon for the LGPL OS using
>> GPL code, and provides a binary package only for A (and B indirectly),
>> and a source package.
>>
>>
>
Other related posts:
