Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: James Hilliard <james.hilliard1@gmail.com>
To: buildroot@buildroot.org
Cc: James Hilliard <james.hilliard1@gmail.com>,
	Fiona Klute <fiona.klute@gmx.de>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH v2 9/9] boot/uboot: add host-python-pkg-resources dependency
Date: Thu, 15 Oct 2026 13:32:43 -0600	[thread overview]
Message-ID: <20261015193243.3299884-9-james.hilliard1@gmail.com> (raw)
In-Reply-To: <20261015193243.3299884-1-james.hilliard1@gmail.com>

U-Boot configurations selecting BR2_TARGET_UBOOT_NEEDS_PYTHON3 already
depend on host-python-setuptools, which provided pkg_resources before
its removal in setuptools 82.

Add the standalone host package under the same condition to preserve
pkg_resources availability for older U-Boot releases and vendor trees,
including versions whose Binman still imports it.

Signed-off-by: James Hilliard <james.hilliard1@gmail.com>

---
Changes v1 -> v2:
  - Tie host-python-pkg-resources to BR2_TARGET_UBOOT_NEEDS_PYTHON3
    instead of BR2_TARGET_UBOOT_USE_BINMAN.
---
 boot/uboot/uboot.mk | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/boot/uboot/uboot.mk b/boot/uboot/uboot.mk
index 96b8cd0d2e..daa841309c 100644
--- a/boot/uboot/uboot.mk
+++ b/boot/uboot/uboot.mk
@@ -268,7 +268,10 @@ UBOOT_MAKE_OPTS += DTC=$(HOST_DIR)/bin/dtc
 endif
 
 ifeq ($(BR2_TARGET_UBOOT_NEEDS_PYTHON3),y)
-UBOOT_DEPENDENCIES += host-python3 host-python-setuptools
+UBOOT_DEPENDENCIES += \
+	host-python3 \
+	host-python-pkg-resources \
+	host-python-setuptools
 endif
 
 ifeq ($(BR2_TARGET_UBOOT_NEEDS_PYLIBFDT),y)
-- 
2.53.0

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2026-10-15 19:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 19:32 [Buildroot] [PATCH v2 1/9] package/python-setuptools: bump to version 84.0.0 James Hilliard
2026-10-15 19:32 ` [Buildroot] [PATCH v2 2/9] package/python-autocommand: add host variant James Hilliard
2026-10-15 19:32 ` [Buildroot] [PATCH v2 3/9] package/python-more-itertools: " James Hilliard
2026-10-15 19:32 ` [Buildroot] [PATCH v2 4/9] package/python-jaraco-context: " James Hilliard
2026-10-15 19:32 ` [Buildroot] [PATCH v2 5/9] package/python-jaraco-functools: " James Hilliard
2026-10-15 19:32 ` [Buildroot] [PATCH v2 6/9] package/python-jaraco-text: " James Hilliard
2026-10-15 19:32 ` [Buildroot] [PATCH v2 7/9] package/python-platformdirs: " James Hilliard
2026-10-15 19:32 ` [Buildroot] [PATCH v2 8/9] package/python-pkg-resources: new host package James Hilliard
2026-10-15 19:32 ` James Hilliard [this message]
2026-10-15 20:23   ` [Buildroot] [PATCH v2 9/9] boot/uboot: add host-python-pkg-resources dependency Fiona Klute via buildroot
2026-10-15 20:26     ` James Hilliard
2026-10-16 15:56       ` Fiona Klute via buildroot
2026-10-15 19:55 ` [Buildroot] [PATCH v2 1/9] package/python-setuptools: bump to version 84.0.0 Thomas Petazzoni via buildroot
2026-10-15 19:58   ` James Hilliard

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=20261015193243.3299884-9-james.hilliard1@gmail.com \
    --to=james.hilliard1@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=fiona.klute@gmx.de \
    --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