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
If you're releasing source, then I think Jozef is correct that you can use
whichever licence you like. However if those sources rely on library G to
work, then you're essentially releasing something that's impossible for
your users to use according to the terms of the licences. From the EPL FAQ
lin
Program B will be released as source. So in this case I can choose the
license of program B independently since it is no "derivative work" of
library G? As far as I read a hint that program B is not "derivative work"
of library G is that I could exchange library G with a different library
which
I've often wondered about this. This restriction seems to mean that any GPL
Clojure library can only ever be for private use. There are a few examples
out there, and this would seem to apply to LightTable as well, since it's
GPL but uses a lot of EPL code. How do they get around this?
With straigh
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
i