mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: Christian Hermann <christian.hermann@hytera.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 02/13] portmap: add license identifier
Date: Mon, 22 Jul 2019 11:37:52 +0200	[thread overview]
Message-ID: <20190722093752.h46tixn234kwzp6g@pengutronix.de> (raw)
In-Reply-To: <20190719121803.28963-2-christian.hermann@hytera.de>

On Fri, Jul 19, 2019 at 02:17:52PM +0200, Christian Hermann wrote:
> Signed-off-by: Christian Hermann <christian.hermann@hytera.de>
> ---
>  rules/portmap.make | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/rules/portmap.make b/rules/portmap.make
> index bece1ea81..600a860b8 100644
> --- a/rules/portmap.make
> +++ b/rules/portmap.make
> @@ -23,6 +23,8 @@ PORTMAP_SUFFIX	:= tgz
>  PORTMAP_URL	:= http://fossies.org/linux/misc/old/portmap-$(PORTMAP_VERSION).$(PORTMAP_SUFFIX)
>  PORTMAP_SOURCE	:= $(SRCDIR)/portmap-$(PORTMAP_VERSION).$(PORTMAP_SUFFIX)
>  PORTMAP_DIR	:= $(BUILDDIR)/$(PORTMAP)
> +PORTMAP_LICENSE := BSD-4-Clause-UC

AND unknown

portmap.c and from_local.c contain some sort of old Sun RPC license,
which apparently don't have an SPDX identifier yet [1].

[1]: https://github.com/Distrotech/rpcbind/blob/master/src/pmap_svc.c

 - Roland

> +PORTMAP_LICENSE_FILES := file://portmap.c;startline=1;endline=32;md5=3758c3c0222f2b08b0f4952dc734e071
>  
>  # ----------------------------------------------------------------------------
>  # Compile
> -- 
> 2.22.0
> 
> 
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> 

-- 
Roland Hieber                     | r.hieber@pengutronix.de     |
Pengutronix e.K.                  | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2019-07-22  9:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19 12:17 [ptxdist] [PATCH 01/13] polkit: " Christian Hermann
2019-07-19 12:17 ` [ptxdist] [PATCH 02/13] portmap: " Christian Hermann
2019-07-22  9:37   ` Roland Hieber [this message]
2019-07-19 12:17 ` [ptxdist] [PATCH 03/13] procps: fix " Christian Hermann
2019-07-22  9:45   ` Roland Hieber
2019-07-19 12:17 ` [ptxdist] [PATCH 04/13] bash: " Christian Hermann
2019-07-22 10:10   ` Roland Hieber
2019-07-19 12:17 ` [ptxdist] [PATCH 05/13] bc: " Christian Hermann
2019-07-22 10:16   ` Roland Hieber
2019-07-19 12:17 ` [ptxdist] [PATCH 06/13] cifs-utils: " Christian Hermann
2019-07-19 12:17 ` [ptxdist] [PATCH 07/13] ddrescue: " Christian Hermann
2019-07-19 12:17 ` [ptxdist] [PATCH 08/13] diffutils: " Christian Hermann
2019-07-19 12:17 ` [ptxdist] [PATCH 09/13] fuse: fix license identifier (split) Christian Hermann
2019-07-19 12:18 ` [ptxdist] [PATCH 10/13] dosfstools: fix license identifier Christian Hermann
2019-07-19 12:18 ` [ptxdist] [PATCH 11/13] file: " Christian Hermann
2019-07-19 12:18 ` [ptxdist] [PATCH 12/13] dnsmasq: add " Christian Hermann
2019-07-19 12:18 ` [ptxdist] [PATCH 13/13] findutils: " Christian Hermann
2019-07-22  9:49 ` [ptxdist] [PATCH 01/13] polkit: " Roland Hieber

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=20190722093752.h46tixn234kwzp6g@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=christian.hermann@hytera.de \
    --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