From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: What license to use for Emacs libraries?
Date: Tue, 18 Aug 2015 17:53:06 -0400 [thread overview]
Message-ID: <jwvegj0qnch.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: 877fosmhmv.fsf@mbork.pl
> Does that mean that releasing Emacs libraries under GPLv2 is illegal?
Pretty much, yes. Since they necessarily link to Emacs's own code which
is GPLv3+, you have to use a license that's compatible with GPLv3+.
Note that GPLv2+ is one such compatible license (as opposed to GPLv2).
> I did a cursory check, and it seems that all libraries built-in in my
> Emacs are GPLv3, but some other are not:
No, they're GPLv3+ (most licenses out there implicitly say "this version
or any later version of it", whereas the GPL is more strict and you
have to explicitly say "GPLv2 or later").
> for instance, my copy of Icicles has GPLv2, and some code on EmacsWiki
> has GPLv2.
If it's stritcly "GPLv2 and no later" then it's probably an error.
> Does that mean that GitHub is a part of a sinister software-patent
> conspiracy or something?
That wouldn't be a surprise, now, would it?
Stefan
next prev parent reply other threads:[~2015-08-18 21:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 21:06 What license to use for Emacs libraries? Marcin Borkowski
2015-08-18 21:48 ` Phillip Lord
2015-08-18 22:01 ` Stefan Monnier
2015-08-18 22:15 ` Phillip Lord
2015-08-18 23:46 ` Robert Thorpe
2015-08-19 14:12 ` Phillip Lord
2015-08-20 7:05 ` Steinar Bang
2015-08-18 23:16 ` Marcin Borkowski
2015-08-19 14:36 ` Tassilo Horn
2015-08-19 21:46 ` Robert Thorpe
2015-08-20 4:44 ` Tassilo Horn
2015-08-19 16:00 ` Phillip Lord
2015-08-18 21:53 ` Stefan Monnier [this message]
2015-08-18 23:21 ` Marcin Borkowski
[not found] ` <mailman.8593.1439940074.904.help-gnu-emacs@gnu.org>
2015-08-19 1:11 ` Stefan Monnier
2015-08-19 16:02 ` 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=jwvegj0qnch.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.