public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] metadata: Add license-mapping.conf for SPDX license mapping
Date: Sun, 13 Nov 2022 16:54:46 +0100	[thread overview]
Message-ID: <ab6837f9351e21e3c596d24294bf0928819f0b4d.camel@gentoo.org> (raw)
In-Reply-To: <ubkpakiqm@gentoo.org>

On Sun, 2022-11-13 at 15:54 +0100, Ulrich Mueller wrote:
> > > > > > On Sun, 13 Nov 2022, Michał Górny wrote:
> 
> > +CC-PD = CC-PDDC
> 
> This one is the wrong way around.

Good catch, thanks.  I've verified the list against SPDX license list
and ::gentoo repo now, and removed "W3C-document" and "GPL-3-with-
autoconf-exception" that we (no longer?) have.

> 
> > +Fair = fairuse
> 
> These are completely different.

Removed.

> 
> > +LPPL-1.3a = LPPL-1.3
> 
> Different version (SPDX doesn't have 1.3, and we don't have 1.3a).

Removed.

> Looks like all versions of the FDL are missing?

To be honest, I'm wondering whether copying the list from cargo-ebuild
is a good idea after all.  Perhaps we should just copy the most common
licenses (i.e. GPLs/BSD/MIT...) that are easy to match, and add other
licenses as we need them (and verify in the process).

I've created a PR to track the current status:
https://github.com/gentoo/gentoo/pull/28256

-- 
Best regards,
Michał Górny



  reply	other threads:[~2022-11-13 15:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13 11:58 [gentoo-dev] [PATCH] metadata: Add license-mapping.conf for SPDX license mapping Michał Górny
2022-11-13 14:54 ` Ulrich Mueller
2022-11-13 15:54   ` Michał Górny [this message]
2022-11-13 17:46 ` Sam James
2022-11-13 18:42   ` Michał Górny

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=ab6837f9351e21e3c596d24294bf0928819f0b4d.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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