From: Andreas Hilboll <lists@hilboll.de>
To: emacs-orgmode@gnu.org
Subject: Re: How to make a non-GPL Org-mode exporter?
Date: Mon, 27 Jul 2015 15:13:00 +0200 [thread overview]
Message-ID: <55B62E5C.3050806@hilboll.de> (raw)
In-Reply-To: <rmi7fpl3fxn.fsf@fnord.ir.bbn.com>
On 27.07.2015 15:09, Greg Troxel wrote:
>
> Rainer M Krug <Rainer@krugs.de> writes:
>
>> These packages all depend on R itself.
>>
>> So isn't this the same as in emacs / elisp? Isn't an exporter / .el file
>> the same as a package in R, something which enhances the original
>> product using a provided interface (the functions) but does not change
>> anything in the original program (R or emacs)?
>
> It's both the same and different.
>
> The legal question of whether R packages are derivative works of R is
> similar to the question of elisp packages that use editing primitives
> are derivative works of emacs.
https://www.gnu.org/licenses/gpl-faq.html#IfInterpreterIsGPL seems to
give an answer:
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.
[...]
Another similar and very common case is to provide libraries with the
interpreter which are themselves interpreted. For instance, Perl comes
with many Perl modules, and a Java implementation comes with many Java
classes. These libraries and the programs that call them are always
dynamically linked together.
A consequence is that if you choose to use GPL'd Perl modules or Java
classes in your program, you must release the program in a
GPL-compatible way, regardless of the license used in the Perl or Java
interpreter that the combined Perl or Java program will run on.
So if I understand this correctly, an R module can be non-GPL if and
only if it does not use any GPL'ed R modules.
Cheers,
Andreas.
next prev parent reply other threads:[~2015-07-27 13:13 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 [this message]
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
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55B62E5C.3050806@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).