From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] python-numpy: correct LICENSE.txt hash value
Date: Mon, 10 Sep 2018 08:56:18 +0200 [thread overview]
Message-ID: <20180910085618.1fe20101@windsurf.home> (raw)
In-Reply-To: <20180909214747.25154-1-giulio.benetti@micronovasrl.com>
Hello,
On Sun, 9 Sep 2018 23:47:47 +0200, Giulio Benetti wrote:
> LICENSE.txt sha256 is wrong. After version bumping from 1.13.3 to 1.15.1
> LICENSE.txt sha256 has not be re-calculated.
>
> New LICENSE.txt lists licenses for bundled libraries:
> - Numpydoc -> 2-clause BSD
> - scipy-sphinx-theme -> 3-clause BSD, PSF and Apache 2.0
> - lapack-lite -> 3-clause BSD
> - tempita -> BSD derived
> - dragon4 -> specific to library, need to refer to dragon4.c file
Then, should we update the license information to list the licenses of
the bundled libraries, or do we keep the fact that python-numpy has a
whole is distributed under BSD-3-Clause ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-10 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 21:47 [Buildroot] [PATCH v2] python-numpy: correct LICENSE.txt hash value Giulio Benetti
2018-09-10 6:56 ` Thomas Petazzoni [this message]
2018-09-10 21:56 ` Giulio Benetti
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=20180910085618.1fe20101@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