Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python-netifaces: allow depending on Python 3
Date: Sat, 22 Nov 2014 19:23:47 +0100	[thread overview]
Message-ID: <20141122192347.3cb69aa3@free-electrons.com> (raw)
In-Reply-To: <1416497530-3035-1-git-send-email-simon.marchi@polymtl.ca>

Dear Simon Marchi,

On Thu, 20 Nov 2014 10:32:10 -0500, Simon Marchi wrote:
> Version 0.10.4 is compatible with python 3.
> 
> Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
> ---
>  package/python-netifaces/Config.in | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/python-netifaces/Config.in b/package/python-netifaces/Config.in
> index 29f9fc3..b660fdb 100644
> --- a/package/python-netifaces/Config.in
> +++ b/package/python-netifaces/Config.in
> @@ -1,6 +1,6 @@
>  config BR2_PACKAGE_PYTHON_NETIFACES
>  	bool "python-netifaces"
> -	depends on BR2_PACKAGE_PYTHON
> +	depends on BR2_PACKAGE_PYTHON || BR2_PACKAGE_PYTHON3

This is no longer necessary. Since commit
http://git.buildroot.net/buildroot/commit/?h=next&id=cd331c1e1d15e7832f6eebc5c1e9c0a2dd34f033,
we have decided that for packages that support both python and python3,
it was not needed to have a dependency anymore, since this dependency
is already in package/Config.in.

Patch applied to the next branch, with this change.

Thanks!

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

      reply	other threads:[~2014-11-22 18:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 15:32 [Buildroot] [PATCH] python-netifaces: allow depending on Python 3 Simon Marchi
2014-11-22 18:23 ` Thomas Petazzoni [this message]

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=20141122192347.3cb69aa3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox