From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/3] openvpn: add license identifier
Date: Tue, 15 Oct 2019 12:40:21 +0200 [thread overview]
Message-ID: <20191015104021.y5motmmpvtbnd2p7@pengutronix.de> (raw)
In-Reply-To: <20191015103006.ilqloxqwaho5p5xz@pengutronix.de>
On Tue, Oct 15, 2019 at 12:30:06PM +0200, Roland Hieber wrote:
> On Wed, Oct 09, 2019 at 04:34:28PM +0200, Hubert Feurstein wrote:
> > Signed-off-by: Hubert Feurstein <h.feurstein@gmail.com>
> > ---
> > rules/openvpn.make | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/rules/openvpn.make b/rules/openvpn.make
> > index ad496d1a7..4035f453f 100644
> > --- a/rules/openvpn.make
> > +++ b/rules/openvpn.make
> > @@ -21,6 +21,10 @@ OPENVPN_SUFFIX := tar.xz
> > OPENVPN_URL := http://swupdate.openvpn.org/community/releases/$(OPENVPN).$(OPENVPN_SUFFIX)
> > OPENVPN_SOURCE := $(SRCDIR)/$(OPENVPN).$(OPENVPN_SUFFIX)
> > OPENVPN_DIR := $(BUILDDIR)/$(OPENVPN)
> > +OPENVPN_LICENSE := GPL-2.0-only
>
> OPENVPN_LICENSE := GPL-2.0-only WITH openvpn-openssl-exception AND BSD-2-Clause AND BSD-3-Clause
>
> The exception is mentioned in COPYING, and SPDX already knows this one :)
> A few files like src/openvpn/base64.c carry BSD-3-Clause headers, and
> the lz4 implementation in src/compat/ is BSD-2-Clause.
>
> > +OPENVPN_LICENSE_FILES := \
> > + file://COPYING;md5=7aee596ed2deefe3e8a861e24292abba \
> > + file://src/openvpn/openvpn.c;startline=1;endline=22;md5=1bb6a64be5c851a32fa98b8f9d6e33f9
>
> file://src/openvpn/base64.c;startline=2;endline=31;md5=f4debd767645b13107fc5912faf2ad8f
> file://src/compat/compat-lz4.c;startline=13;endline=38;md5=5f66cf078523624965e41518eed881e2
And COPYRIGHT.GPL, that contains the actual GPL license text.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-10-15 10:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 14:34 [ptxdist] [PATCH 1/3] wget: " Hubert Feurstein
2019-10-09 14:34 ` [ptxdist] [PATCH 2/3] openvpn: " Hubert Feurstein
2019-10-15 10:30 ` Roland Hieber
2019-10-15 10:40 ` Michael Olbrich [this message]
2019-10-09 14:34 ` [ptxdist] [PATCH 3/3] cpufrequtils: " Hubert Feurstein
2019-10-15 10:32 ` Roland Hieber
2019-10-15 10:14 ` [ptxdist] [PATCH 1/3] wget: " Roland Hieber
2019-10-25 7:37 ` 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=20191015104021.y5motmmpvtbnd2p7@pengutronix.de \
--to=m.olbrich@pengutronix.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