Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gr-osmosdr: bump to 0.2.0
Date: Fri, 10 Apr 2020 22:23:49 +0200	[thread overview]
Message-ID: <20200410222349.111429ea@windsurf.home> (raw)
In-Reply-To: <20200410150111.15360-1-gwenj@trabucayre.com>

On Fri, 10 Apr 2020 17:01:11 +0200
Gwenhael Goavec-Merou <gwenj@trabucayre.com> wrote:

> From: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>
> 
> Since, gr-osmosdr is python3 only, drop everything related to python2.
> python-cheetah is no more mandatory, so drop this too.
> 
> Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>
> ---
>  package/gr-osmosdr/Config.in       | 1 +
>  package/gr-osmosdr/gr-osmosdr.hash | 2 +-
>  package/gr-osmosdr/gr-osmosdr.mk   | 8 ++++----
>  3 files changed, 6 insertions(+), 5 deletions(-)
> 
> diff --git a/package/gr-osmosdr/Config.in b/package/gr-osmosdr/Config.in
> index 1e80137f35..3d12540c7d 100644
> --- a/package/gr-osmosdr/Config.in
> +++ b/package/gr-osmosdr/Config.in
> @@ -1,6 +1,7 @@
>  config BR2_PACKAGE_GR_OSMOSDR
>  	bool "gr-osmosdr"
>  	depends on BR2_PACKAGE_GNURADIO
> +	depends on BR2_PACKAGE_PYTHON3

Why do you add this dependency? The package itself only requires
host-python3, not the target python.

However, the BR2_PACKAGE_GR_OSMOSDR_PYTHON option would indeed need
this dependency.

Am I missing something ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-04-10 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10 15:01 [Buildroot] [PATCH] package/gr-osmosdr: bump to 0.2.0 Gwenhael Goavec-Merou
2020-04-10 20:23 ` Thomas Petazzoni [this message]
2020-04-11  9:27   ` Gwenhael Goavec-Merou

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=20200410222349.111429ea@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