From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: EPL licence for emacs extension distributed via ELPA.
Date: Mon, 28 Jan 2013 09:17:58 -0500 [thread overview]
Message-ID: <jwv8v7dtn80.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: CAEo=ZYZtaHGyCXNqrtFWnLwPeiVr1MnbAzRAHtYBVjWVUr=r0g@mail.gmail.com
> I am going to do an emacs extension on emacs lisp and clojure
> languages. The problem is that I should include external clojure
> project (it is used as a library), distribued on the terms of Eclipse
> Public License 1.0 with a tiny modification.
I'm not sure what the above really means, but the following guidelines
might help clarify:
- Elisp code basically needs to be distributed under a license
compatible with the GPL since it necessary links to the rest of Emacs
which is GPL'd.
- Same for Emacs extensions written in C.
- Emacs code can interact with external applications via pipes without
any restriction on those applications's licensing model.
- You can distribute as a single package a combination of GPL'd Elisp/C
code together with some other code using a different license: the mere
fact of putting it all into a single tarball does not force you to use
the same licenses for all the files.
> 1) Is it possible to distribute via ELPA (in repositories like
> marmalade or melpa) my code with GPL licence together with this
> EPL code?
I don't see a particular problem in this regard from any ELPA repository
(including GNU ELPA).
Stefan
prev parent reply other threads:[~2013-01-28 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 6:39 EPL licence for emacs extension distributed via ELPA kostafey
2013-01-24 7:30 ` Bastien
[not found] ` <CAEo=ZYbJ6cBcEM4VkEyXJjcf1OM5sbjCt+s2taPZ1N6dPmFdXg@mail.gmail.com>
2013-01-24 8:16 ` kostafey
2013-01-24 9:59 ` Bastien
2013-01-24 21:28 ` Glenn Morris
2013-01-25 5:35 ` kostafey
2013-01-27 3:26 ` Glenn Morris
2013-01-28 14:17 ` Stefan Monnier [this message]
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=jwv8v7dtn80.fsf-monnier+gmane.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@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.