From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/python-periphery: new package
Date: Sat, 22 Jun 2019 19:28:12 +0200 [thread overview]
Message-ID: <20190622192812.3abffc71@windsurf> (raw)
In-Reply-To: <1561055893-22140-1-git-send-email-pjtexier@koncepto.io>
On Thu, 20 Jun 2019 20:38:13 +0200
Pierre-Jean Texier <pjtexier@koncepto.io> wrote:
> Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
> ---
> Changes v1 -> v2
> - remove 'v' prefix in PYTHON_PERIPHERY_VERSION
>
> Scanpy was not used because the archive in pythonhosted
> does not contain the license file.
>
> With the github repo : make python-periphery-legal-info
> >>> python-periphery 1.1.1 Collecting legal info
> LICENSE: OK (sha256: db1bea825e728d8bcdf6c220d79c74370a9fcb63a4f9153c2cece2b63e177aa4)
>
> DEVELOPERS | 1 +
> package/Config.in | 1 +
> package/python-periphery/Config.in | 7 +++++++
> package/python-periphery/python-periphery.hash | 3 +++
> package/python-periphery/python-periphery.mk | 13 +++++++++++++
> 5 files changed, 25 insertions(+)
> create mode 100644 package/python-periphery/Config.in
> create mode 100644 package/python-periphery/python-periphery.hash
> create mode 100644 package/python-periphery/python-periphery.mk
Applied to master, thanks. It would be good to notify upstream that the
LICENSE file is missing in the "official" tarball available from PyPi.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-06-22 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 18:38 [Buildroot] [PATCH v2 1/1] package/python-periphery: new package Pierre-Jean Texier
2019-06-22 17:28 ` Thomas Petazzoni [this message]
2019-06-22 18:07 ` Pierre-Jean Texier
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=20190622192812.3abffc71@windsurf \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.