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 19:42:19 +0100	[thread overview]
Message-ID: <96483765099dbd059d500bec9a17572c08e79b20.camel@gentoo.org> (raw)
In-Reply-To: <0494AB01-75DA-4438-AB13-BC2E189FDF91@gentoo.org>

On Sun, 2022-11-13 at 17:46 +0000, Sam James wrote:
> 
> > On 13 Nov 2022, at 11:58, Michał Górny <mgorny@gentoo.org> wrote:
> > 
> > Add a file defining mapping of SPDX-2.0 license identifiers to Gentoo
> > ebuild licenses.  This was originally discussed on Gentoo Bugzilla [1],
> > the submitted to the gentoo-dev ml [2].
> > 
> > The proposed file uses the common key-value format used for
> > configuration files.  Currently only `spdx-to-ebuild` section is defined
> > but other kinds of mapping can be added in the future.  As described
> > in the top comment, it provides the ability to map SPDX-2.0 license
> > identifiers along with the `+` and `WITH` operators to arbitrary
> > Gentoo LICENSE strings (including all-of and any-of groups).
> > 
> > The initial list is taken from cargo-ebuild's license.rs [3],
> > courtesy of Leonardo H. Neumann and Georgy Yakovlev.  A parser for this
> > file format is implemented in pycargoebuild [4].
> > 
> > [1] https://bugs.gentoo.org/706472
> > [2] https://archives.gentoo.org/gentoo-dev/message/01924bb71411696dce04445d85da508d
> > [3] https://gitweb.gentoo.org/proj/cargo-ebuild.git/tree/src/license.rs?id=b4314edc5bb672f5e94dcbc996f443e98fdb4dba
> > [4] https://github.com/projg2/pycargoebuild/
> > 
> > Signed-off-by: Michał Górny <mgorny@gentoo.org>
> > ---
> > metadata/license-mapping.conf | 171 ++++++++++++++++++++++++++++++++++
> > 1 file changed, 171 insertions(+)
> > create mode 100644 metadata/license-mapping.conf
> > 
> 
> I like the idea.
> 
> If/when we do this:
> - Should this be in a GLEP?
> 

I don't think we need a GLEP, the comment on top should be sufficient to
explain how it's supposed to work.

-- 
Best regards,
Michał Górny



      reply	other threads:[~2022-11-13 18:42 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
2022-11-13 17:46 ` Sam James
2022-11-13 18:42   ` Michał Górny [this message]

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=96483765099dbd059d500bec9a17572c08e79b20.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