From: Andreas Hilboll <lists@hilboll.de>
To: emacs-orgmode@gnu.org
Subject: Re: How to make a non-GPL Org-mode exporter?
Date: Tue, 28 Jul 2015 12:14:29 +0200 [thread overview]
Message-ID: <55B75605.1090204@hilboll.de> (raw)
In-Reply-To: <87k2tkzl28.fsf@gmail.com>
On 28.07.2015 11:30, Oleh Krehel wrote:
> Andreas Hilboll <lists@hilboll.de> writes:
>
>>>> Look here:
>>>> https://en.wikipedia.org/w/index.php?title=GNU_General_Public_License§ion=11#Libraries
>>>>
>>>> Most useful quote:
>>>>
>>>>> The Free Software Foundation (which holds the copyright of several
>>>>> notable GPL-licensed software products and of the license text itself)
>>>>> asserts that an executable which uses a dynamically linked library is
>>>>> indeed a derivative work. This does not however apply to separate
>>>>> programs communicating with one another.
>
>>> thanks for this link and excerpt. I could argue that the key word in
>>> the excerpt is "executable". I cannot see how code written in elisp
>>> itself would need to be GPL.
>>
>> Exactly. To quote again
>> https://www.gnu.org/licenses/gpl-faq.html#IfInterpreterIsGPL:
>>
>> When the interpreter just interprets a language, the answer is no.
>> The interpreted program, to the interpreter, is just data; a free
>> software license like the GPL, based on copyright law, cannot limit
>> what data you use the interpreter on. You can run it on any data
>> (interpreted program), any way you like, and there are no
>> requirements about licensing that data to anyone.
>
> Just to link the paragraph exactly below the one you quoted
>
>> However, when the interpreter is extended to provide “bindings” to
>> other facilities (often, but not necessarily, libraries), the
>> interpreted program is effectively linked to the facilities it uses
>> through these bindings. So if these facilities are released under the
>> GPL, the interpreted program that uses them must be released in a
>> GPL-compatible way. The JNI or Java Native Interface is an example of
>> such a binding mechanism; libraries that are accessed in this way are
>> linked dynamically with the Java programs that call them. These
>> libraries are also linked with the interpreter. If the interpreter is
>> linked statically with these libraries, or if it is designed to link
>> dynamically with these specific libraries, then it too needs to be
>> released in a GPL-compatible way.
>
> Indeed, the Emacs interpreter gives "bindings" to all Emacs facilities,
> which are GPL, and the interpreted program that uses them must be
> released in a GPL-compatible way.
I would interpret this as
"As long as I write pure elisp and don't require' and GPL'ed part of
Emacs, I can release my code under any license I want. If I do
require' any part of Emacs, I have to go the GPL path."
If I'm wrong with this interpretation, please explain why.
-- Andreas.
next prev parent reply other threads:[~2015-07-28 10:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 12:10 How to make a non-GPL Org-mode exporter? Marcin Borkowski
2015-07-27 12:16 ` Oleh Krehel
2015-07-27 13:02 ` Rainer M Krug
2015-07-27 13:09 ` Greg Troxel
2015-07-27 13:13 ` Andreas Hilboll
2015-07-27 13:30 ` Rainer M Krug
2015-07-27 14:05 ` Marcin Borkowski
2015-07-27 14:03 ` Marcin Borkowski
2015-07-28 12:33 ` Paul Rudin
2015-07-27 12:39 ` Daniele Nicolodi
2015-07-27 16:59 ` Marcin Borkowski
2015-07-27 18:02 ` Nick Dokos
2015-07-27 18:12 ` Marcin Borkowski
2015-07-27 18:45 ` Daniele Nicolodi
2015-07-28 7:55 ` Oleh Krehel
2015-07-29 14:54 ` Aaron Ecay
2015-07-30 10:08 ` Oleh Krehel
2015-07-27 13:05 ` Greg Troxel
2015-07-27 14:32 ` Marcin Borkowski
2015-07-27 13:58 ` Scott Randby
2015-07-27 16:32 ` Marcin Borkowski
2015-07-27 15:13 ` Eric S Fraga
2015-07-27 16:01 ` Marcin Borkowski
2015-07-27 16:12 ` Oleh Krehel
2015-07-27 17:12 ` Marcin Borkowski
2015-07-27 17:13 ` Thomas S. Dye
2015-07-27 16:54 ` Eric S Fraga
2015-07-27 17:04 ` Marcin Borkowski
2015-07-27 18:38 ` Eric S Fraga
2015-07-28 8:07 ` Oleh Krehel
2015-07-28 9:00 ` Eric S Fraga
2015-07-28 9:00 ` Oleh Krehel
2015-07-28 10:38 ` Eric S Fraga
2015-07-28 9:20 ` Andreas Hilboll
2015-07-28 9:30 ` Oleh Krehel
2015-07-28 10:14 ` Andreas Hilboll [this message]
2015-07-28 10:29 ` Oleh Krehel
2015-07-27 18:32 ` Richard Lawrence
2015-08-04 15:04 ` Phillip Lord
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55B75605.1090204@hilboll.de \
--to=lists@hilboll.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.