From: ludo@gnu.org (Ludovic Courtès)
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 30836-done@debbugs.gnu.org
Subject: bug#30836: [PATCH 2/3] guix import elpa: use #f for license
Date: Sun, 18 Mar 2018 23:25:41 +0100 [thread overview]
Message-ID: <87d101nhqy.fsf@gnu.org> (raw)
In-Reply-To: <m1bmflhjoz.fsf@ordinateur-de-catherine--konrad.home> (Konrad Hinsen's message of "Sun, 18 Mar 2018 09:27:56 +0100")
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
>>
>>> Elpa doesn't supply license information. The current importer pretends that
>>> everything is GPL3, which is not true. The importer should not invent license
>>> information.
>>
>> Do you have examples of packages on ELPA that are not GPLv3+? I don’t
>> know if this is the case, but I wouldn’t be surprised if it had a policy
>> of requiring GPLv3+ given that Emacs itself is GPLv3+.
>
> The ELPA importer is also used for MELPA, which has no license
> requirements. The package that motivated this patch is Deft, which is
> MIT-licensed:
>
> https://jblevins.org/projects/deft/
>
> If GNU ELPA guarantees GPL3, we could keep the old behavior for that
> but use #f for MELPA and stable MELPA.
Good idea. Commit 9bb1838c3f982dfb84ba24eb2f727cb39ee5805c does that.
Thanks!
Ludo’.
prev parent reply other threads:[~2018-03-18 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 13:53 [bug#30836] [PATCH 2/3] guix import elpa: use #f for license Konrad Hinsen
2018-03-17 21:29 ` Ludovic Courtès
2018-03-18 8:27 ` Konrad Hinsen
2018-03-18 22:25 ` Ludovic Courtès [this message]
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=87d101nhqy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30836-done@debbugs.gnu.org \
--cc=konrad.hinsen@fastmail.net \
/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.