> On 13 Nov 2022, at 11:58, Michał Górny <[email protected]> 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 <[email protected]> > --- > 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? - It needs pkgcheck support for e.g. invalid entries, duplicates.
signature.asc
Description: Message signed with OpenPGP
