From: Jai Vetrivelan <jaivetrivelan@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Xah Lee <xah@xahlee.org>, 54351 <54351@debbugs.gnu.org>
Subject: [bug#54351] [PATCH] gnu: Add emacs-xah-fly-keys.
Date: Sun, 13 Mar 2022 08:33:30 +0530 [thread overview]
Message-ID: <8735jmy2nx.fsf@gmail.com> (raw)
In-Reply-To: <8853d5968ea3bd8245079e5e69ed90c2a04d8b75.camel@telenet.be> (Maxime Devos's message of "Sat, 12 Mar 2022 18:59:31 +0100")
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
Hello Maxime,
On 2022-03-12, 18:59 +0100, Maxime Devos <maximedevos@telenet.be> wrote:
> Emacs is GPL3+ (according to guix show). This extension of Emacs is
> GPL2-only (according to the package definition). Seems like the author
> intended it to be free software, but accidentally made a license
> incompatibility?
Is there any requirement for third party elisp packages to be /gpl3-or-later/?
<https://lists.gnu.org/archive/html/emacs-devel/2017-07/msg01069.html>
talks only about packages in the ELPA (xah-fly-keys is not a part of any
ELPA). One package in emacs-xyz.scm is /gpl2-only/, which upstream has
updated to /gpl3+/. [1]
My original concern was the second sentence of the license string.
> Additionally, IIRC, the GPL has some requirements about including a
> copy of the GPL.
>
> I assume these issue would be easy to correct by contacting upstream.
>
> I looked a little further and saw
> <https://github.com/xahlee/xah-fly-keys/issues/28>, so I guess that
> the .el is just a little out-of-date.
I have contacted the author off-list regarding clarification on license.
[1] https://github.com/rlister/org-present/pull/39
--
Jai Vetrivelan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2022-03-13 3:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 12:23 [bug#54351] [PATCH] gnu: Add emacs-xah-fly-keys Jai Vetrivelan
2022-03-12 17:59 ` Maxime Devos
2022-03-13 3:03 ` Jai Vetrivelan [this message]
2022-03-13 9:08 ` Maxime Devos
2022-03-13 10:48 ` Jai Vetrivelan
2022-03-13 11:09 ` Maxime Devos
2022-03-13 9:20 ` Maxime Devos
2022-06-07 19:56 ` bug#54351: " Nicolas Goaziou
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735jmy2nx.fsf@gmail.com \
--to=jaivetrivelan@gmail.com \
--cc=54351@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--cc=xah@xahlee.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/guix.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).