From: "Guðni Már Gilbert" <gudnimar@noxmedical.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] python3-setuptools: drop python3-2to3 from RDEPENDS
Date: Thu, 20 Jun 2024 04:19:21 -0700 [thread overview]
Message-ID: <6942.1718882361902473385@lists.openembedded.org> (raw)
In-Reply-To: <B2D135A1-D55A-43D2-8830-3DA7393D44C5@arm.com>
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
On Thu, Jun 20, 2024 at 09:57 AM, Ross Burton wrote:
>
> That does beg the question of why setuptools was part of a minimal image
> in the first place? Was that a requirement of yours, or is something
> pulling setuptools into all images?
>
> Ross
Hi Ross,
My minimal image requires gobject-introspection which for some reason is requiring setuptools at runtime. This was not a requirement in Kirkstone, and only appeared when I migrated my project to Scarthgap.
See: https://git.openembedded.org/openembedded-core/tree/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.78.1.bb?h=scarthgap#n192
I haven't looked into if this is correct or what part of gobject-introspection requires setuptools at runtime. On Kirkstone, my image ran fine without both distutils and setuptools at runtime.
[-- Attachment #2: Type: text/html, Size: 1056 bytes --]
next prev parent reply other threads:[~2024-06-20 11:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 17:03 [PATCH] python3-setuptools: drop python3-2to3 from RDEPENDS Guðni Már Gilbert
2024-06-19 17:06 ` Guðni Már Gilbert
2024-06-20 9:57 ` [OE-core] " Ross Burton
2024-06-20 11:19 ` Guðni Már Gilbert [this message]
2024-06-20 11:30 ` Guðni Már Gilbert
2024-06-20 12:46 ` [OE-core] " Ross Burton
2024-06-21 7:47 ` Alexander Kanavin
2024-06-21 11:14 ` Guðni Már Gilbert
2024-06-24 10:58 ` [OE-core] " Ross Burton
2024-06-24 13:15 ` Guðni Már Gilbert
2024-06-27 8:17 ` Guðni Már Gilbert
2024-06-27 8:22 ` [OE-core] " Alexander Kanavin
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=6942.1718882361902473385@lists.openembedded.org \
--to=gudnimar@noxmedical.com \
--cc=openembedded-core@lists.openembedded.org \
/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