From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/python-bsdiff4: new packge
Date: Sat, 25 Apr 2020 22:53:58 +0200 [thread overview]
Message-ID: <20200425225358.1dcd475b@windsurf.home> (raw)
In-Reply-To: <20200227204335.25823-1-asafka7@gmail.com>
Hello,
On Thu, 27 Feb 2020 22:43:35 +0200
Asaf Kahlon <asafka7@gmail.com> wrote:
> License file isn't shipped with the package, so PKG-INFO
> is used instead.
I am concerned by the license here.
> +PYTHON_BSDIFF4_VERSION = 1.1.9
> +PYTHON_BSDIFF4_SOURCE = bsdiff4-$(PYTHON_BSDIFF4_VERSION).tar.gz
> +PYTHON_BSDIFF4_SITE = https://files.pythonhosted.org/packages/39/34/bd2ae6cd4b2a5d3af9173a9d7f6ecd2723ea7b0401ad807a0c7e7b50faa3
> +PYTHON_BSDIFF4_LICENSE = BSD-2-Clause
> +PYTHON_BSDIFF4_LICENSE_FILES = PKG-INFO
PKG-INFO only says "BSD", and nothing in the source code indicates what
is the license.
The only indication is in core.c, which contains:
/*
The code below is mostly derived from cx_bsdiff (written by Anthony
Tuininga, http://cx-bsdiff.sourceforge.net/). The cx_bsdiff code in
turn was derived from bsdiff, the standalone utility produced for BSD
which can be found at http://www.daemonology.net/bsdiff.
*/
If we visit http://cx-bsdiff.sourceforge.net/ we can find
http://cx-bsdiff.sourceforge.net/LICENSE.txt, which is not the
BSD-2-Clause, but some weird license called the "BSD Protection
License", which is known by SPDX as BSD-Protection:
https://spdx.org/licenses/BSD-Protection.html
Could you try to clarify what is the license of this package ? It would
be really good for PyPi to be a bit more "strict" in the description of
the licenses.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-04-25 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 20:43 [Buildroot] [PATCH 1/1] package/python-bsdiff4: new packge Asaf Kahlon
2020-04-25 20:53 ` Thomas Petazzoni [this message]
2020-04-26 18:03 ` Asaf Kahlon
2020-04-27 5:35 ` Thomas Petazzoni
2020-04-27 15:52 ` Asaf Kahlon
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=20200425225358.1dcd475b@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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