From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] [RFC] Manual.md: use SPDX expressions for license=
Date: Thu, 13 Jun 2024 20:05:01 +0200 [thread overview]
Message-ID: <20240613180501.C5A8E27B5C@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50819@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
There is an updated pull request by classabbyamp against master on the void-packages repository
https://github.com/classabbyamp/void-packages spdx
https://github.com/void-linux/void-packages/pull/50819
[RFC] Manual.md: use SPDX expressions for license=
see also: https://github.com/void-linux/void-packages/issues/48303
xlint supports parsing this since leahneukirchen/xtools#322
SPDX expressions are more expressive and accurate than the comma-separated format, and WITH has already been usable for a long time.
I propose that existing multi-licence strings be changed in batches (if someone wants to spend the time) or as templates are modified.
@void-linux/pkg-committers
A patch file from https://github.com/void-linux/void-packages/pull/50819.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-spdx-50819.patch --]
[-- Type: text/x-diff, Size: 1468 bytes --]
From ac1f4952ecf34328f0186524a5066c4d06d00d61 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Thu, 13 Jun 2024 13:49:51 -0400
Subject: [PATCH] Manual.md: use SPDX expressions for license=
xlint supports parsing this since leahneukirchen/xtools#322
SPDX expressions are more expressive and accurate than the
comma-separated format, and WITH has already been usable for a long
time.
---
Manual.md | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/Manual.md b/Manual.md
index 507a18729459bb..1cc0ea701b592c 100644
--- a/Manual.md
+++ b/Manual.md
@@ -439,7 +439,12 @@ The list of mandatory variables for a template:
- <a id="var_license"></a>
`license` A string matching the license's [SPDX Short identifier](https://spdx.org/licenses),
`Public Domain`, or string prefixed with `custom:` for other licenses.
-Multiple licenses should be separated by commas, Example: `GPL-3.0-or-later, custom:Hugware`.
+Multiple licenses should be listed as an
+[SPDX license expression](https://spdx.github.io/spdx-spec/v3.0/annexes/SPDX-license-expressions/)
+(examples: `MIT OR Apache-2.0`, `MIT AND (LGPL-2.1-or-later OR BSD-3-Clause)`).
+Usage of `AND`, `OR`, `WITH`, and `()` are supported by xlint. The legacy
+comma-separated format should be converted when encountered (example:
+`GPL-3.0-or-later, custom:Hugware`).
Empty meta-packages that don't include any files
and thus have and require no license should use
next prev parent reply other threads:[~2024-06-13 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 18:03 [PR PATCH] " classabbyamp
2024-06-13 18:03 ` classabbyamp
2024-06-13 18:05 ` classabbyamp [this message]
2024-06-13 19:49 ` 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=20240613180501.C5A8E27B5C@inbox.vuxu.org \
--to=classabbyamp@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).