From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Marcus Hoffmann via buildroot <buildroot@buildroot.org>
Cc: James Hilliard <james.hilliard1@gmail.com>,
Angelo Compagnucci <angelo.compagnucci@gmail.com>,
Marcus Hoffmann <buildroot@bubu1.eu>,
Asaf Kahlon <asafka7@gmail.com>
Subject: Re: [Buildroot] [PATCH 2/2] package/python-can: needs PYTHON3_CURSES
Date: Mon, 22 Jul 2024 22:37:48 +0200 [thread overview]
Message-ID: <20240722223748.5893f728@windsurf> (raw)
In-Reply-To: <20240213123753.2471309-2-buildroot@bubu1.eu>
On Tue, 13 Feb 2024 13:37:53 +0100
Marcus Hoffmann via buildroot <buildroot@buildroot.org> wrote:
> The can.viewer tool requires curses support. [1]
>
> [1] https://github.com/hardbyte/python-can/blob/v4.3.1/can/viewer.py#L44-L53
>
> Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu>
> ---
> package/python-can/Config.in | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/python-can/Config.in b/package/python-can/Config.in
> index 61955a2b00..106da4560c 100644
> --- a/package/python-can/Config.in
> +++ b/package/python-can/Config.in
> @@ -1,5 +1,6 @@
> config BR2_PACKAGE_PYTHON_CAN
> bool "python-can"
> + select BR2_PACKAGE_PYTHON3_CURSES # runtime for can.viewer tool
I am not 100% sure on this one. Do we want to make this dependency
mandatory, while it is only needed for a viewer tool, which probably
most users of python-can won't use?
I see two alternatives here:
1. Leave things are they are today, i.e let users figure out that they
need to enable curses support for the viewer.
2. Add an explicit BR2_PACKAGE_PYTHON_CAN_VIEWER option, which selects
BR2_PACKAGE_PYTHON3_CURSES and enables the installation of the viewer
tool. When this option is disabled, viewer.py is not installed (or
removed if disabling installation is not possible)
Thoughts? This is not a hard feeling on my side.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-07-22 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 12:37 [Buildroot] [PATCH 1/2] package/python-can/Config.in: sort selects Marcus Hoffmann via buildroot
2024-02-13 12:37 ` [Buildroot] [PATCH 2/2] package/python-can: needs PYTHON3_CURSES Marcus Hoffmann via buildroot
2024-07-22 20:37 ` Thomas Petazzoni via buildroot [this message]
2024-08-22 10:01 ` Marcus Hoffmann via buildroot
2024-07-22 20:35 ` [Buildroot] [PATCH 1/2] package/python-can/Config.in: sort selects Thomas Petazzoni via buildroot
2024-08-31 16:45 ` Peter Korsgaard
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=20240722223748.5893f728@windsurf \
--to=buildroot@buildroot.org \
--cc=angelo.compagnucci@gmail.com \
--cc=asafka7@gmail.com \
--cc=buildroot@bubu1.eu \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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