4 ms·

Why?

by elteto 8y ago

Why?

dymk 8y ago
Because anything you build with it is automatically GPL as well.
tom_ 8y ago
If you create a program that links with a GPL library, the program as a whole must itself also be GPL - which is not always acceptable. See section 5 of the GPL: https://www.gnu.org/licenses/gpl.html https://www.gnu.org/licenses/gpl.html "You may convey a work based on the Program ... provided that you also meet all of these conditions: ... c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy"
- hak8or 8y ago
  Not always. I believe a common understanding is if it statically links with GPL code, then it spreads to your code. If it dynamically links then your program is not hit with GPL, as the user is able to change the dynamic library with their own. If what you dewxribed were the case, then the Tivoization lawsuit would have went differently instead of GPLv3 coming out.
  - dragonwriter 8y ago
    > I believe a common understanding is if it statically links with GPL code, then it spreads to your code. If it dynamically links then your program is not hit with GPL The FSF disagrees: https://www.gnu.org/licenses/gpl-faq.en.html#GPLStaticVsDynamic https://www.gnu.org/licenses/gpl-faq.en.html#GPLStaticVsDyna... > If what you dewxribed were the case, then the Tivoization lawsuit would have went differently instead of GPLv3 coming out. The anti-Tivoization clause of GPLv3 doesn't deal with a linking issue, it deals with the fact that even if the device maker releases code for modifications under GPLv2, that doesn't let the user modify and replace the code on the device if the device is locked down so as not to accept modified code, and the user hasn't been provided with the appropriate incantations to unlock it.
  - gmueckl 8y ago
    You are confusing the terms.of the GPL and LGPL. The GPL does require a program linked to a GPL library to be distributed under the GPL as well. This requirement is not in the LGPL. There, you only have to provide the user with the means to exchange the LGPL library with a different, possibly modified one.
  - deleted 8y ago
    [deleted]
sovande 8y ago
Because you have to license your iOS App as GPL if you want to use this framework. GPL is not compatible with the AppStore terms. They say they plan to dual license with a (free) commercial license in the future...

Why?

by elteto 8y ago

Why?

dymk 8y ago

Because anything you build with it is automatically GPL as well.

tom_ 8y ago

If you create a program that links with a GPL library, the program as a whole must itself also be GPL - which is not always acceptable. See section 5 of the GPL: https://www.gnu.org/licenses/gpl.html https://www.gnu.org/licenses/gpl.html "You may convey a work based on the Program ... provided that you also meet all of these conditions: ... c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy"

hak8or 8y ago
Not always. I believe a common understanding is if it statically links with GPL code, then it spreads to your code. If it dynamically links then your program is not hit with GPL, as the user is able to change the dynamic library with their own. If what you dewxribed were the case, then the Tivoization lawsuit would have went differently instead of GPLv3 coming out.
- dragonwriter 8y ago
  > I believe a common understanding is if it statically links with GPL code, then it spreads to your code. If it dynamically links then your program is not hit with GPL The FSF disagrees: https://www.gnu.org/licenses/gpl-faq.en.html#GPLStaticVsDynamic https://www.gnu.org/licenses/gpl-faq.en.html#GPLStaticVsDyna... > If what you dewxribed were the case, then the Tivoization lawsuit would have went differently instead of GPLv3 coming out. The anti-Tivoization clause of GPLv3 doesn't deal with a linking issue, it deals with the fact that even if the device maker releases code for modifications under GPLv2, that doesn't let the user modify and replace the code on the device if the device is locked down so as not to accept modified code, and the user hasn't been provided with the appropriate incantations to unlock it.
- gmueckl 8y ago
  You are confusing the terms.of the GPL and LGPL. The GPL does require a program linked to a GPL library to be distributed under the GPL as well. This requirement is not in the LGPL. There, you only have to provide the user with the means to exchange the LGPL library with a different, possibly modified one.
- deleted 8y ago
  [deleted]

sovande 8y ago

Because you have to license your iOS App as GPL if you want to use this framework. GPL is not compatible with the AppStore terms. They say they plan to dual license with a (free) commercial license in the future...