From: Maxime Devos <maximedevos@telenet.be>
To: Jai Vetrivelan <jaivetrivelan@gmail.com>, 54351@debbugs.gnu.org
Subject: [bug#54351] [PATCH] gnu: Add emacs-xah-fly-keys.
Date: Sat, 12 Mar 2022 18:59:31 +0100 [thread overview]
Message-ID: <8853d5968ea3bd8245079e5e69ed90c2a04d8b75.camel@telenet.be> (raw)
In-Reply-To: <874k43tl50.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
Jai Vetrivelan schreef op za 12-03-2022 om 17:53 [+0530]:
> There's no COPYING or LICENSE file in the repository, and the emacs-
> lisp
> file states:
>
> ┌────
> │ ;; License: GPL v2. Tell your friends to buy a copy.
> └────
>
> Please let me know if this package is considered free software to be
> included in Guix. Thank you.
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?
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.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-03-12 18:00 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 [this message]
2022-03-13 3:03 ` Jai Vetrivelan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8853d5968ea3bd8245079e5e69ed90c2a04d8b75.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=54351@debbugs.gnu.org \
--cc=jaivetrivelan@gmail.com \
/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/guix.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.