4 ms·
https://www.eclipse.org/legal/eplfaq.php#GPLCOMPATIBLE https://www.eclipse.org/legal/eplfaq.php#GPLCOMPATIBLE Based upon the position of the Free Software Foun
by lemming 8y ago
https://www.eclipse.org/legal/eplfaq.php#GPLCOMPATIBLE https://www.eclipse.org/legal/eplfaq.php#GPLCOMPATIBLE
Based upon the position of the Free Software Foundation, you may not combine EPL 1.0 and GPL code in any scenario where linking exists between code made available under those licenses. The above applies to both GPL version 2 and GPL version 3.
Since Clojure itself and its core library are EPL, this means you basically cannot write GPL code with Clojure.
- bachmeier 8y agoThere are no restrictions on what you do with GPL software if you're not distributing it. Here's what the FSF has to say[1]: "If I only make copies of a GPL-covered program and run them, without distributing or conveying them to others, what does the license require of me? (#NoDistributionRequirements) Nothing. The GPL does not place any conditions on this activity." The whole point of the GPL is to guarantee that the user can do anything they want with the software. The only limitations on GPL software are with respect to distribution.
- fulafel 8y agoSo is the Eclipse FAQ wrong, or does the EPL forbid this private use of EPL'd code in a non-distribution scenario? It sounds to me like the FAQ is wrong, since it quotes the FSF's position as the foundation of its argument. edit: apparently a twist is that GPL is considered a pure copyright license, and so covers only distribution, but the EPL is broader. It starts with "ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT". So apparently this makes it a kind of contract and not just a copyright licese.