|
Having just reread the the GPL v2 FAQ I say, Chris got it exactly
right. But, I understand why Jonathan said he is wrong. Lets take what Chris said in two parts. 1) Chris said, "To say that a license is GPL compatible means that code licensed under that license may be incorporated in/used by GPL licensed software." This is covered in the FAQ by the fallowing Q and As: Q - What does it mean to say a license is “compatible with the GPL”. http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#WhatDoesCompatMean Q - If I add a module to a GPL-covered program, do I have to use the GPL as the license for my module? http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLModuleLicense (Short answer: it must be GPL or GPL-compatible.) Q - If a program released under the GPL uses plug-ins, what are the requirements for the licenses of a plug-in. http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLAndPlugins (Short answer: if linked they probably need to be GPL or GPL-compatible.) Q - If license for a module Q has a requirement that's incompatible with the GPL, but the requirement applies only when Q is distributed by itself, not when Q is included in a larger program, does that make the license GPL-compatible? Can I combine or link Q with a GPL-covered program? http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLIncompatibleAlone (Short answer: Q when alone must also be GPL-compatible). 2) Chris said, "Code that is GPL licensed may only be used within code that is likewise GPL licensed. (This is the whole 'viral' nature of the GPL.)" This is covered in the FAQ by the fallowing Q and As: Q - If a library is released under the GPL (not the LGPL), does that mean that any program which uses it has to be under the GPL? A - Yes, because the program as it is actually run includes the library. http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#IfLibraryIsGPL Q - You have a GPL'ed program that I'd like to link with my code to build a proprietary program. Does the fact that I link with your program mean I have to GPL my program? A - Yes. http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#LinkingWithGPL Q - Can I apply the GPL when writing a plug-in for a non-free program? http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLPluginsInNF (Note: in this case it is your GPL plug-in so you can release it under more than one license or a modified license. But the copies released under the GPL would be viral as Chris said.) Q - In an object-oriented language such as Java, if I use a class that is GPL'ed without modifying, and subclass it, in what way does the GPL affect the larger program? A - Subclassing is creating a derivative work. Therefore, the terms of the GPL affect the whole program where you create a subclass of a GPL'ed class. http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#OOPLang Q - Can I release a non-free program that's designed to load a GPL-covered plug-in? (Short answer: if linked the GPL must be followed when the main program is distributed for use with these plug-ins) http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#NFUseGPLPlugins Jonathan said, "If I can add a module to a library (or a "plugin" for that matter) which is not GPL licensed but GPL compatible, of course I can create an entire frontend that is GPL compatible but not GPL licensed." That is similar to the last question quoted from the FAQ: "Can I release a non-free program that's designed to load a GPL-covered plug-in?" Jonathan is correct in thinking that the frontend could just be GPL compatible. What I think he may be missing though is that the combination of the frontend and module or library must be GPL not just GPL compatible. (Assuming enough linking.) In the combination, the module or library acts as Chris said and results in a GPL combination. Just as a GPL frontend with a GPL compatible module or library would also make the combination GPL. Either way, the parts apart from the combination must be usable as GPL, which is what compatible means. If one part is not usable as GPL then the GPL has been violated. In part 2 above, Chris said, "used within code." If he had said, "used with code" he would be wrong. The part is "within" the combination so the combination must be GPL even if any other part, even the main program, is just compatible. Jerry Jonathan Morgan wrote: On Tue, Mar 17, 2009 at 10:45 AM, Chris Little <chris...@crosswire.org> wrote: |
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
