From: Andreas Pretzsch <apr@cn-eng.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 4/4] zip: add license information and license file for report generation
Date: Tue, 04 Oct 2016 17:50:27 +0200 [thread overview]
Message-ID: <1475596227.7146.3.camel@ws-apr.office.loc> (raw)
In-Reply-To: <20161004133043.bpsma4pipclvxlqi@pengutronix.de>
On Di, 2016-10-04 at 15:30 +0200, Michael Olbrich wrote:
> On Mon, Oct 03, 2016 at 09:01:24PM +0200, Andreas Pretzsch wrote:
> > License information is pretty much the same as with unzip, just a newer
> > revision of the (BSD-like) Info-ZIP license (here: version 2007-Mar-4).
> >
> > Signed-off-by: Andreas Pretzsch <apr@cn-eng.de>
> > ---
> > rules/zip.make | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/rules/zip.make b/rules/zip.make
> > index 09ba4a0..ec59e72 100644
> > --- a/rules/zip.make
> > +++ b/rules/zip.make
> > @@ -26,6 +26,8 @@ ZIP := zip$(ZIP_AVERSION)
> > ZIP_URL := $(call ptx/mirror, SF, infozip/$(ZIP_ARCHIVE))
> > ZIP_SOURCE := $(SRCDIR)/$(ZIP_ARCHIVE)
> > ZIP_DIR := $(BUILDDIR)/$(ZIP)
> > +ZIP_LICENSE := Info-ZIP, BSD-like
>
> Nothing with ',' here please. I think only 'Info-ZIP' is correct here, the
> 'BSD-like' is just a different description for the same license, right? And
> 'Info-ZIP' ist the correct SPDX identifiere.
All correct. Just followed the way it is stated in unzip.
But true, descriptive texts ("BSD-like") do not belong here, but should
come out of the real license, resp. from a link/addition to it, on
another place. Not from above tag.
I'll make a V2 of the patch, this time both for unzip and zip packages.
You prefer this patch combined or separate ?
--
carpe noctem engineering
Ingenieurbuero fuer Hard- & Software-Entwicklung Andreas Pretzsch
Dipl.-Ing. (FH) Andreas Pretzsch Tel. +49-(0)7307-936088-1
Lange Strasse 28a Fax: +49-(0)7307-936088-9
89250 Senden, Germany email: apr@cn-eng.de
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-10-04 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 19:01 [ptxdist] [PATCH 0/4] gnupg, screen, squashfs-tools, zip: add license tags Andreas Pretzsch
2016-10-03 19:01 ` [ptxdist] [PATCH 1/4] gnupg: add license information (GPL-3.0+) Andreas Pretzsch
2016-10-03 19:01 ` [ptxdist] [PATCH 2/4] screen: add license information (GPL-2.0+) Andreas Pretzsch
2016-10-03 19:01 ` [ptxdist] [PATCH 3/4] squashfs-tools: " Andreas Pretzsch
2016-10-03 19:01 ` [ptxdist] [PATCH 4/4] zip: add license information and license file for report generation Andreas Pretzsch
2016-10-04 13:30 ` Michael Olbrich
2016-10-04 15:50 ` Andreas Pretzsch [this message]
2016-10-04 16:40 ` [ptxdist] [PATCH v2] " Andreas Pretzsch
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=1475596227.7146.3.camel@ws-apr.office.loc \
--to=apr@cn-eng.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