From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: Thomas Perale via buildroot <buildroot@buildroot.org>,
James Hilliard <james.hilliard1@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/python-yarl: add missing select
Date: Sat, 16 Aug 2025 22:52:01 +0200 [thread overview]
Message-ID: <20250816225201.10b98623@windsurf> (raw)
In-Reply-To: <20250816202153.3376159-1-thomas.perale@mind.be>
On Sat, 16 Aug 2025 22:21:53 +0200
Thomas Perale <thomas.perale@mind.be> wrote:
> Good to know, my reasoning was that other package in that same case seemed to
> select `BR2_PACKAGE_HOST_PYTHON_CYTHON`:
>
> - python-kmod/Config.in
> - python-dbus-fast/Config.in
> - python-rgbmatrix/Config.in
>
> So, if you prefer to not include the 'select' I will send a v2 and remove my
> series that did the same for python-propcache
> (https://lore.kernel.org/r/<20250813201639.2443921-1-thomas.perale@mind.be>).
Indeed to me right now the consensus has been to _not_ add those
selects for host packages. The Config.in.host option is only to allow a
user to explicitly enable a host package through "make menuconfig".
Thanks!
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
prev parent reply other threads:[~2025-08-16 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 13:01 [Buildroot] [PATCH 1/2] package/python-yarl: add missing select Thomas Perale via buildroot
2025-08-16 13:01 ` [Buildroot] [PATCH 2/2] python-yarl: bump to v1.20.1 Thomas Perale via buildroot
2025-08-16 17:52 ` [Buildroot] [PATCH 1/2] package/python-yarl: add missing select Thomas Petazzoni via buildroot
2025-08-16 20:21 ` Thomas Perale via buildroot
2025-08-16 20:52 ` Thomas Petazzoni via buildroot [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=20250816225201.10b98623@windsurf \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=thomas.perale@mind.be \
--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 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.