Gentoo Archives: gentoo-dev

From: "Michał Górny" <mgorny@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [PATCH] metadata: Add license-mapping.conf for SPDX license mapping
Date: Sun, 13 Nov 2022 18:42:27
Message-Id: 96483765099dbd059d500bec9a17572c08e79b20.camel@gentoo.org
In Reply to: Re: [gentoo-dev] [PATCH] metadata: Add license-mapping.conf for SPDX license mapping by Sam James
1 On Sun, 2022-11-13 at 17:46 +0000, Sam James wrote:
2 >
3 > > On 13 Nov 2022, at 11:58, Michał Górny <mgorny@g.o> wrote:
4 > >
5 > > Add a file defining mapping of SPDX-2.0 license identifiers to Gentoo
6 > > ebuild licenses. This was originally discussed on Gentoo Bugzilla [1],
7 > > the submitted to the gentoo-dev ml [2].
8 > >
9 > > The proposed file uses the common key-value format used for
10 > > configuration files. Currently only `spdx-to-ebuild` section is defined
11 > > but other kinds of mapping can be added in the future. As described
12 > > in the top comment, it provides the ability to map SPDX-2.0 license
13 > > identifiers along with the `+` and `WITH` operators to arbitrary
14 > > Gentoo LICENSE strings (including all-of and any-of groups).
15 > >
16 > > The initial list is taken from cargo-ebuild's license.rs [3],
17 > > courtesy of Leonardo H. Neumann and Georgy Yakovlev. A parser for this
18 > > file format is implemented in pycargoebuild [4].
19 > >
20 > > [1] https://bugs.gentoo.org/706472
21 > > [2] https://archives.gentoo.org/gentoo-dev/message/01924bb71411696dce04445d85da508d
22 > > [3] https://gitweb.gentoo.org/proj/cargo-ebuild.git/tree/src/license.rs?id=b4314edc5bb672f5e94dcbc996f443e98fdb4dba
23 > > [4] https://github.com/projg2/pycargoebuild/
24 > >
25 > > Signed-off-by: Michał Górny <mgorny@g.o>
26 > > ---
27 > > metadata/license-mapping.conf | 171 ++++++++++++++++++++++++++++++++++
28 > > 1 file changed, 171 insertions(+)
29 > > create mode 100644 metadata/license-mapping.conf
30 > >
31 >
32 > I like the idea.
33 >
34 > If/when we do this:
35 > - Should this be in a GLEP?
36 >
37
38 I don't think we need a GLEP, the comment on top should be sufficient to
39 explain how it's supposed to work.
40
41 --
42 Best regards,
43 Michał Górny