All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package: add python-raven
Date: Thu, 2 Nov 2017 21:32:08 +0100	[thread overview]
Message-ID: <20171102213208.4d4236aa@windsurf> (raw)
In-Reply-To: <20171102163419.24155-1-joseph.kogut@gmail.com>

Hello,

Thanks for this new contribution! Looks pretty good, just a few minor
nits or questions.

First, the title of the commit should be:

	python-raven: new package

(We like to have consistent naming for commit titles, as it allows to
more easily grep through the Git history).

On Thu,  2 Nov 2017 09:34:18 -0700, Joseph Kogut wrote:
> Signed-off-by: Joseph Kogut <joseph.kogut@gmail.com>
> ---
>  package/Config.in                      |  1 +
>  package/python-raven/Config.in         |  6 ++++++
>  package/python-raven/python-raven.hash |  3 +++
>  package/python-raven/python-raven.mk   | 14 ++++++++++++++
>  4 files changed, 24 insertions(+)

Please include the change to the DEVELOPERS file in the same patch, no
need to make it a separate patch.

> diff --git a/package/python-raven/Config.in b/package/python-raven/Config.in
> new file mode 100644
> index 0000000000..1fbd1d8c03
> --- /dev/null
> +++ b/package/python-raven/Config.in
> @@ -0,0 +1,6 @@
> +config BR2_PACKAGE_PYTHON_RAVEN
> +	bool "python-raven"

It really doesn't have *any* runtime dependency on other Python
modules? I.e if you build just python-raven and the minimal python
interpreter, it works?

I.e, if you build:

BR2_PACKAGE_PYTHON=y
BR2_PACKAGE_PYTHON_RAVEN=y

does it build and run on the target?

> +PYTHON_RAVEN_VERSION = 6.2.1

There is a 6.3.0 version available, any reason not to use this one ?

> +PYTHON_RAVEN_SOURCE = raven-$(PYTHON_RAVEN_VERSION).tar.gz
> +PYTHON_RAVEN_SITE = https://pypi.python.org/packages/c1/97/38e74c7521737c965281b43440b274955e211b1d5319c256d8525d9d2cad
> +PYTHON_RAVEN_SETUP_TYPE = setuptools
> +PYTHON_RAVEN_LICENSE = BSD-3-Clause
> +PYTHON_RAVEN_LICENSE_FILES = LICENSE

Other than that looks good. Could you respin an updated version that
takes into account those comments?

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2017-11-02 20:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 16:34 [Buildroot] [PATCH 1/2] package: add python-raven Joseph Kogut
2017-11-02 16:34 ` [Buildroot] [PATCH 2/2] DEVELOPERS: add myself as maintainer for python-raven Joseph Kogut
2017-11-02 20:32 ` Thomas Petazzoni [this message]
2017-11-03 19:08   ` [Buildroot] [PATCH 1/2] package: add python-raven Joseph Kogut
2017-11-03 20:00     ` Thomas Petazzoni

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=20171102213208.4d4236aa@windsurf \
    --to=thomas.petazzoni@free-electrons.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.