unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Jai Vetrivelan <jaivetrivelan@gmail.com>
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 10:20:43 +0100	[thread overview]
Message-ID: <4904c91bfe40bbabcfe204c42bb56cc6054ee537.camel@telenet.be> (raw)
In-Reply-To: <8735jmy2nx.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 735 bytes --]

Jai Vetrivelan schreef op zo 13-03-2022 om 08:33 [+0530]:
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>

GPL-3-only should also be fine I think (at least, as long as the Emacs
in Guix isn't updated to a new Emacs that is GPL4+)).  I guess that
gpl2+ is also fine in Guix (at least for ‘old’ emacs packages that were
written with ‘old’ GPL2+ Emacen in mind, perhaps also for other
packages but I don't know the legalities of that at all) though I
recommend the authors of these packages to update anyway (just in case,
and because of <https://www.gnu.org/licenses/rms-why-gplv3.html>).

Greetings,
Maxime.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2022-03-13  9:21 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
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 [this message]
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=4904c91bfe40bbabcfe204c42bb56cc6054ee537.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=54351@debbugs.gnu.org \
    --cc=jaivetrivelan@gmail.com \
    --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).