<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Having just reread the the GPL v2 FAQ I say, Chris got it exactly
right. But, I understand why Jonathan said he is wrong.<br>
<br>
Lets take what Chris said in two parts.<br>
<br>
1) Chris said, "To say that a license is GPL compatible means that
code licensed under that license may be<br>
incorporated in/used by GPL licensed software."<br>
<br>
This is covered in the FAQ by the fallowing Q and As:<br>
<br>
Q - What does it mean to say a license is “compatible with the GPL”.<br>
<a class="moz-txt-link-freetext" href="http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#WhatDoesCompatMean">http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#WhatDoesCompatMean</a><br>
<br>
Q - If I add a module to a GPL-covered program, do I have to use the
GPL as the license for my module?<br>
<a class="moz-txt-link-freetext" href="http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLModuleLicense">http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLModuleLicense</a><br>
(Short answer: it must be GPL or GPL-compatible.)<br>
<br>
Q - If a program released under the GPL uses plug-ins, what are the
requirements for the licenses of a plug-in.<br>
<a class="moz-txt-link-freetext" href="http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLAndPlugins">http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLAndPlugins</a><br>
(Short answer: if linked they probably need to be GPL or
GPL-compatible.)<br>
<br>
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?<br>
<a class="moz-txt-link-freetext" href="http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLIncompatibleAlone">http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLIncompatibleAlone</a><br>
(Short answer: Q when alone must also be GPL-compatible). <br>
<br>
2) Chris said, "Code that is GPL licensed may only be used within
code that is likewise GPL licensed. (This is the whole<br>
'viral' nature of the GPL.)"<br>
<br>
This is covered in the FAQ by the fallowing Q and As:<br>
<br>
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?<br>
A - Yes, because the program as it is actually run includes the
library. <br>
<a class="moz-txt-link-freetext" href="http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#IfLibraryIsGPL">http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#IfLibraryIsGPL</a><br>
<br>
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?<br>
A - Yes.<br>
<a class="moz-txt-link-freetext" href="http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#LinkingWithGPL">http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#LinkingWithGPL</a><br>
<br>
Q - Can I apply the GPL when writing a plug-in for a non-free program?<br>
<a class="moz-txt-link-freetext" href="http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLPluginsInNF">http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLPluginsInNF</a><br>
(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.)<br>
<br>
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?<br>
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. <br>
<a class="moz-txt-link-freetext" href="http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#OOPLang">http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#OOPLang</a><br>
<br>
Q - Can I release a non-free program that's designed to load a
GPL-covered plug-in?<br>
(Short answer: if linked the GPL must be followed when the main program
is distributed for use with these plug-ins)<br>
<a class="moz-txt-link-freetext" href="http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#NFUseGPLPlugins">http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#NFUseGPLPlugins</a><br>
<br>
Jonathan said, "If I can add a module to a library (or a "plugin" for
that matter)<br>
which is not GPL licensed but GPL compatible, of course I can create<br>
an entire frontend that is GPL compatible but not GPL licensed."<br>
<br>
That is similar to the last question quoted from the FAQ:<br>
"Can I release a non-free program that's designed to load a GPL-covered
plug-in?"<br>
<br>
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.<br>
<br>
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. <br>
<br>
Jerry<br>
<br>
Jonathan Morgan wrote:
<blockquote
cite="mid:f6aec790903170430y47f8ad8dsb0ad6a72cfb82c16@mail.gmail.com"
type="cite">
<pre wrap="">On Tue, Mar 17, 2009 at 10:45 AM, Chris Little <a class="moz-txt-link-rfc2396E" href="mailto:chrislit@crosswire.org"><chrislit@crosswire.org></a> wrote:
</pre>
<blockquote type="cite"><br>
<pre wrap="">This is completely incorrect (more specifically backwards). To say that a
license is GPL compatible means that code licensed under that license may be
incorporated in/used by GPL licensed software. 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.)
</pre>
</blockquote>
<pre wrap=""><!---->
It is not backward, it is a pure statement of facts, which you can
find quite clearly in the GPL v2 FAQ
<a class="moz-txt-link-rfc2396E" href="http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLModuleLicense"><http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLModuleLicense></a>.
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.
Fundamentally, the GPL cannot require you to do anything more than are
in its terms of license, which is that changes are distributed in
accordance with the license. You have complete and sole ownership of
those changes or of that "derivative work", but if you distribute it
they must be distributed in a way that satisfies the terms of the GPL.
As I have complete ownership of those changes, I can release them
under any terms I like that do not conflict with the GPL. I can grant
any additional permissions I like (such as releasing under a MIT
license or into the public domain). This doesn't require legalese, it
just requires a knowledge of ownership and what I can do with things
that I own.
Oh, BTW, BPBible does not link with the header files, though I think
it is still reasonable to call it a derivative work under the terms of
the GPL.
Jon
_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
<br>
</body>
</html>