From: HiPhish <HiPhish@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Ambiguity of multi-license notation
Date: Sat, 20 Jan 2024 19:17:15 +0100 [thread overview]
Message-ID: <20240120181715.DE50A23A8E@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48303@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
New comment by HiPhish on void-packages repository
https://github.com/void-linux/void-packages/issues/48303#issuecomment-1902219826
Comment:
Updating xlint would be good, but if we want to support more complex expressions that involve parentheses it gets much more complicated. One solution would be to internally ignore any parentheses, then we only validate the individual license identifiers, but not the entire expression. Or we shell out to a dedicated validator.
And the manual should be updated to recommend SPDX expressions instead of comma.
next prev parent reply other threads:[~2024-01-20 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 18:01 [ISSUE] Amiguity " HiPhish
2024-01-20 18:10 ` Ambiguity " classabbyamp
2024-01-20 18:17 ` HiPhish [this message]
2024-02-10 7:11 ` 0x5c
2024-02-10 7:19 ` classabbyamp
2024-02-11 9:16 ` 0x5c
2024-02-11 9:17 ` 0x5c
2024-05-12 1:48 ` github-actions
2024-05-12 16:58 ` classabbyamp
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=20240120181715.DE50A23A8E@inbox.vuxu.org \
--to=hiphish@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).