Github messages for voidlinux
 help / color / mirror / Atom feed
From: HiPhish <HiPhish@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Amiguity of multi-license notation
Date: Sat, 20 Jan 2024 19:01:40 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48303@inbox.vuxu.org> (raw)

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

New issue by HiPhish on void-packages repository

https://github.com/void-linux/void-packages/issues/48303

Description:
If a package is released under the terms of two licenses the manual says

> Multiple licenses should be separated by commas, Example: `GPL-3.0-or-later, custom:Hugware`.

However, this does not make it clear whether *either* of the license terms apply, or whether *both* apply. An example of a package where both licenses apply is `picom` which is under the terms of both the MPL-2.0 *and* MIT licenses.

This ambiguity could be avoided by using [SPDX expressions](https://spdx.github.io/spdx-spec/v2.3/SPDX-license-expressions/) to combine multiple licenses. These expressions can be arbitrarily complex and cover combinations of licenses (`AND` and `OR`) as well as exceptions (`WITH`) and grouping with parentheses. In the case of picom the SPDX expression is `MPL-2.0 AND MIT`. In fact, there is an SPDX file in the repo that contains this license: https://github.com/yshui/picom/blob/197b4bd396590cb5df61eb54ec6a1dadf1115a5d/LICENSE.spdx

             reply	other threads:[~2024-01-20 18:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-20 18:01 HiPhish [this message]
2024-01-20 18:10 ` Ambiguity " classabbyamp
2024-01-20 18:17 ` HiPhish
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48303@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).