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 5/5] package/python-mwscrape: new package
Date: Fri, 7 Oct 2016 15:33:26 +0200	[thread overview]
Message-ID: <20161007153326.576d6e64@free-electrons.com> (raw)
In-Reply-To: <20161006044858.27768-5-bernd.kuhls@t-online.de>

Hello,

On Thu,  6 Oct 2016 06:48:58 +0200, Bernd Kuhls wrote:

> +config BR2_PACKAGE_PYTHON_MWSCRAPE
> +	bool "python-mwscrape"
> +	select BR2_PACKAGE_PYTHON_COUCHDB
> +	select BR2_PACKAGE_PYTHON_FUTURES if BR2_PACKAGE_PYTHON
> +	select BR2_PACKAGE_PYTHON_MWCLIENT
> +	select BR2_PACKAGE_PYTHON_PYLRU

I suspect some of those are runtime dependencies. Could you double
check this?

> +PYTHON_MWSCRAPE_DEPENDENCIES = python-couchdb \
> +	$(if $(BR2_PACKAGE_PYTHON),python-futures,) \
> +	python-mwclient \
> +	python-pylru

And update this accordingly?

Thanks!

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

  reply	other threads:[~2016-10-07 13:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06  4:48 [Buildroot] [PATCH 1/5] package/python-couchdb: new package Bernd Kuhls
2016-10-06  4:48 ` [Buildroot] [PATCH 2/5] package/python-futures: " Bernd Kuhls
2016-10-07 13:31   ` Thomas Petazzoni
2016-10-06  4:48 ` [Buildroot] [PATCH 3/5] package/python-pylru: " Bernd Kuhls
2016-10-07 13:31   ` Thomas Petazzoni
2016-10-06  4:48 ` [Buildroot] [PATCH 4/5] package/python-mwclient: " Bernd Kuhls
2016-10-07 13:32   ` Thomas Petazzoni
2016-10-06  4:48 ` [Buildroot] [PATCH 5/5] package/python-mwscrape: " Bernd Kuhls
2016-10-07 13:33   ` Thomas Petazzoni [this message]
2016-10-07 13:30 ` [Buildroot] [PATCH 1/5] package/python-couchdb: " 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=20161007153326.576d6e64@free-electrons.com \
    --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.