This is, I think, incorrect. The GPL includes a standard "linking
exception". Look for this part....

A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.


If what you say is correct, for example, it would be impossible to
produce GPL code which would run on Windows or Mac since in all of these
cases the OS itself is non-GPL (nor even free). But it is possible to do
this -- you can run linux, for example, in windows user space with no
legal issues, or Emacs, or cygwin. Or, indeed, write a GPL program in
Java.

In the case of Clojure, you can link a GPL library to Clojure itself.
So, in this case, library G really is relevant. If G is GPLv3 and B uses
it, then B must also be GPLv3 because of this. So, the issue is, what
"other Clojure libraries" is A dependent on. If it is dependant on the
"standard interface" there is not a problem. If not, then I don't think
the program can be legally distributed.

Phil



Jozef Wagner <[email protected]> writes:

> Do you want to distribute binaries (.class files) of the program B? If not,
> you may license your sources in any license you want. If yes, then it will
> be possible only if the library G has a linking exception in its license
> [1], as the clojure itself is EPL so it does not matter how the library A
> is licensed. Without linking exception  you cannot distribute the combined
> work from EPL and GPL sources [2] [3].
>
> [1] http://en.wikipedia.org/wiki/GPL_linking_exception
> [2] https://www.eclipse.org/legal/eplfaq.php#GPLCOMPATIBLE
> [3] http://mmilinkov.wordpress.com/2010/04/06/epl-gpl-commentary/
>
> Jozef
>
>
> On Sat, May 10, 2014 at 5:44 PM, Gunnar Völkel <
> [email protected]> wrote:
>
>> I have written a Clojure library A which is licensed under Eclipse Public
>> License (EPL) as usual which depends on other Clojure libraries with EPL
>> license.
>> In a different program B I use library A and another library G which is
>> licensed under GPLv3.
>>
>> Now, the question arises which license I am allowed to use (or even must
>> use) for program B.
>>
>> As far as I have read it is not possible to license B under EPL because
>> library G is licensed under GPLv3.
>> Leaving the only option to license program B under GPLv3 - does that sound
>> correct to you?
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Clojure" group.
>> To post to this group, send email to [email protected]
>> Note that posts from new members are moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> [email protected]
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>

-- 
Phillip Lord,                           Phone: +44 (0) 191 222 7827
Lecturer in Bioinformatics,             Email: [email protected]
School of Computing Science,            
http://homepages.cs.ncl.ac.uk/phillip.lord
Room 914 Claremont Tower,               skype: russet_apples
Newcastle University,                   twitter: phillord
NE1 7RU                                 

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to [email protected]
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to