From: Uwe Brauer <oub@mat.ucm.es>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: Uwe Brauer <oub@mat.ucm.es>, Richard Stallman <rms@gnu.org>,
emacs-devel@gnu.org
Subject: Re: is GPL2 or later enough for having a package in ELPA?
Date: Mon, 10 Jul 2023 14:09:59 +0200 [thread overview]
Message-ID: <874jmc9dd4.fsf@mat.ucm.es> (raw)
In-Reply-To: 875y6saz7x.fsf@web.de
[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]
> Uwe Brauer <oub@mat.ucm.es> writes:
> this was discussed during the drafting of GPLv3 a lot: a later version
> means a license released after GPL 2, but only if it is similar in
> spirit to the license (that’s written in the GPLv2 and GPLv3).
> So no blanket permission. For any future GPL the FSF will have to make
> sure that it’s similar in spirit, to GPL v2 and GPL v3, otherwise using
> old code under these new licenses would risk legal attacks, and then no
> one in their right mind would use those licenses.
> GPLv2+ and GPLv3+ are (upwards) compatible. If you have GPLv3+ files, then
> the project as a whole must be GPLv3+ (or GPLv3, but please don’t leave
> out the "or later", that creates a world of pain if you want to use the
> later version at some point — and if history is a teacher, you will want
> to).
Ok, thanks for clarifying. I usually have the «+» always included.
Just to make sure, to have a LICENSE file in the main directory that
states all files (without specifying them) are under GPL3+ is not
enough.
Ah, and another thing I just found out a few files don't even have a
license included, that is why I thought a LICENSE could come in handy.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2023-07-10 12:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 15:51 is GPL2 or later enough for having a package in ELPA? Uwe Brauer
2023-07-09 3:26 ` Yuchen Pei
2023-07-10 1:58 ` Richard Stallman
2023-07-10 7:49 ` Uwe Brauer
2023-07-10 9:27 ` Dr. Arne Babenhauserheide
2023-07-10 12:09 ` Uwe Brauer [this message]
2023-07-10 18:48 ` Dr. Arne Babenhauserheide
2023-07-12 3:04 ` Richard Stallman
2023-07-12 15:08 ` Uwe Brauer
2023-07-17 2:20 ` Richard Stallman
2023-07-17 6:07 ` Uwe Brauer
2023-07-17 7:21 ` Dr. Arne Babenhauserheide
2023-07-19 2:19 ` Richard Stallman
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=874jmc9dd4.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=arne_bab@web.de \
--cc=emacs-devel@gnu.org \
--cc=rms@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.