From: Philip McGrath <philip@philipmcgrath.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 58621-done@debbugs.gnu.org
Subject: [bug#58621] [PATCH 0/3] import/utils: spdx-string->license: Match case-insensitively and support '+' operator.
Date: Fri, 18 Nov 2022 15:21:52 -0500 [thread overview]
Message-ID: <7474321.EvYhyI6sBW@bastet> (raw)
In-Reply-To: <877czscr61.fsf_-_@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]
Hi,
On Friday, November 18, 2022 8:45:26 AM EST Ludovic Courtès wrote:
> Hi,
>
> Applied all three patches. I added trivial tests for
> ‘spdx-string->license’ and changed ‘substring’ to ‘string-drop-right’,
> which I find clearer.
>
Thanks!
> Philip McGrath <philip@philipmcgrath.com> skribis:
> > + (and (string-suffix? "+" str)
> > + ;; We try the form with the + to support deprecated identifiers
> > for + ;; GNU licenses (see above). Here, we handle other uses
> > of +. + (spdx-string->license
> > + (substring str 0 (- (string-length str) 1)))))))
>
> I guess we can remove the “+” forms from the alist now?
>
I think we still want the "+" forms in the alist so that we continue convert
"GPL-2.0+" as though it were "GPL-2.0-or-later", not "GPL-2.0-only".
Some upstreams probably wrote "GPL-2.0" out of confusion even though they
intended to allow "any later version" (and maybe even said so in prose), which
is why the "+" operator was deprecated for GNU licenses.
If upstream wrote "GPL-2.0+", though, that does communicate "or, at your
option, any later version"; since that's the more compatible case, it seemed
useful to retain that information when we have it.
Ideally, upstream projects should move away from the deprecated identifiers
(the Racket tooling I've written will complain), but they still seem to come
up often enough in the wild to be worth handling as special cases.
-Philip
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-18 20:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 4:55 [bug#58621] [PATCH 0/3] import/utils: spdx-string->license: Match case-insensitively and support '+' operator Philip McGrath
2022-10-19 5:04 ` [bug#58621] [PATCH 1/3] import/utils: spdx-string->license: Fix incorrect docstring Philip McGrath
2022-10-19 5:04 ` [bug#58621] [PATCH 2/3] import/utils: spdx-string->license: Match case-insensitively Philip McGrath
2022-10-19 5:04 ` [bug#58621] [PATCH 3/3] import/utils: spdx-string->license: Support '+' operator Philip McGrath
2022-11-18 13:45 ` bug#58621: [PATCH 0/3] import/utils: spdx-string->license: Match case-insensitively and support " Ludovic Courtès
2022-11-18 20:21 ` Philip McGrath [this message]
2022-11-20 10:49 ` [bug#58621] " Ludovic Courtès
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=7474321.EvYhyI6sBW@bastet \
--to=philip@philipmcgrath.com \
--cc=58621-done@debbugs.gnu.org \
--cc=ludo@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 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).