mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Bruno Thomsen <bruno.thomsen@gmail.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 6/6] gnupg: add license files and update spdx identifiers
Date: Fri, 29 Jul 2022 12:38:06 +0200	[thread overview]
Message-ID: <YuO4jtFguU1C9Wp3@pengutronix.de> (raw)
In-Reply-To: <20220729092654.3861-6-bruno.thomsen@gmail.com>

On Fri, Jul 29, 2022 at 11:26:54AM +0200, Bruno Thomsen wrote:
> Add license files with md5 hash.
> Add more complete SPDX identifiers based on package COPYING* files.
> 
> Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
> ---
>  rules/gnupg.make | 9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/rules/gnupg.make b/rules/gnupg.make
> index acb4d2082050..09132832791b 100644
> --- a/rules/gnupg.make
> +++ b/rules/gnupg.make
> @@ -24,7 +24,14 @@ GNUPG_URL	:= \
>  	ftp://ftp.gnupg.org/gcrypt/gnupg/$(GNUPG).$(GNUPG_SUFFIX)
>  GNUPG_SOURCE	:= $(SRCDIR)/$(GNUPG).$(GNUPG_SUFFIX)
>  GNUPG_DIR	:= $(BUILDDIR)/$(GNUPG)
> -GNUPG_LICENSE	:= GPL-3.0-or-later
> +GNUPG_LICENSE	:= GPL-2.0-only AND GPL-3.0-only AND LGPL-2.1-only AND LGPL-3.0-only

I think, those are all '-or-later'.

> +GNUPG_LICENSE_FILES := \
> +	file://COPYING;md5=189af8afca6d6075ba6c9e0aa8077626 \
> +	file://COPYING.CC0;md5=5364f88a4fb7a4d2d24c350fa08ddbad \

This is only used for tests, so I think we can skip it.

> +	file://COPYING.GPL2;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
> +	file://COPYING.LGPL21;md5=3c9636424f4ef15d6cb24f934190cfb0 \
> +	file://COPYING.LGPL3;md5=a2b6bf2cb38ee52619e60f30a1fc7257 \
> +	file://COPYING.other;md5=a231ccb4bb5b0651e08464e4e6f846d3

The licenses here should be listed as well. I'm seeing:

 - MIT
 - something for a test file, so skip it
 - Spencer-86
 - BSD-2-Clause-Views
 - Unicode-DFS-2016 (I think)

Michael

>  
>  # ----------------------------------------------------------------------------
>  # Prepare
> -- 
> 2.37.1
> 
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2022-07-29 10:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29  9:26 [ptxdist] [PATCH 1/6] npth: version bump 1.5 -> 1.6 Bruno Thomsen
2022-07-29  9:26 ` [ptxdist] [PATCH 2/6] libgpg-error: version bump 1.42 -> 1.45 Bruno Thomsen
2022-08-04 15:14   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-29  9:26 ` [ptxdist] [PATCH 3/6] libgcrypt: version bump 1.8.8 -> 1.10.1 Bruno Thomsen
2022-08-04 15:14   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-29  9:26 ` [ptxdist] [PATCH 4/6] libksba: version bump 1.3.5 -> 1.6.0 Bruno Thomsen
2022-08-04 15:14   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-29  9:26 ` [ptxdist] [PATCH 5/6] gnupg: version bump 2.2.23 -> 2.3.7 Bruno Thomsen
2022-08-05  7:50   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-29  9:26 ` [ptxdist] [PATCH 6/6] gnupg: add license files and update spdx identifiers Bruno Thomsen
2022-07-29 10:38   ` Michael Olbrich [this message]
2022-08-04 15:14 ` [ptxdist] [APPLIED] npth: version bump 1.5 -> 1.6 Michael Olbrich

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=YuO4jtFguU1C9Wp3@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=bruno.thomsen@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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