From: Ross Burton <ross.burton@arm.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/3] shared-mime-info: remove python3native dependency
Date: Fri, 26 Jun 2026 16:13:24 +0100 [thread overview]
Message-ID: <20260626151325.1735368-2-ross.burton@arm.com> (raw)
In-Reply-To: <20260626151325.1735368-1-ross.burton@arm.com>
This was added in the shared-mime-info 1.15 upgrade[1] with no rationale,
I suspect it was for itstool-native which is no longer used[2]. At least,
none of the dependencies would need python3-native over the host python3.
[1] oe-core 09ef7f8e4b9 ("shared-mime-info: upgrade 1.10 -> 1.15")
[2] oe-core 8ca8687b336 ("shared-mime-info: drop itstool-native from DEPENDS")
Signed-off-by: Ross Burton <ross.burton@arm.com>
---
meta/recipes-support/shared-mime-info/shared-mime-info_2.4.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-support/shared-mime-info/shared-mime-info_2.4.bb b/meta/recipes-support/shared-mime-info/shared-mime-info_2.4.bb
index f307aca35dd..f27061d5d1a 100644
--- a/meta/recipes-support/shared-mime-info/shared-mime-info_2.4.bb
+++ b/meta/recipes-support/shared-mime-info/shared-mime-info_2.4.bb
@@ -13,7 +13,7 @@ SRC_URI = "git://gitlab.freedesktop.org/xdg/shared-mime-info.git;protocol=https;
file://0002-Handle-build-with-older-versions-of-GCC.patch"
SRCREV = "9a6d6b8e963935f145f3a1ef446552de6996dada"
-inherit meson pkgconfig gettext python3native mime
+inherit meson pkgconfig gettext mime
EXTRA_OEMESON = " \
-Dupdate-mimedb=true \
--
2.43.0
next prev parent reply other threads:[~2026-06-26 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 15:13 [PATCH 1/3] blueprint-compiler: inherit python3-dir not python3targetconfig Ross Burton
2026-06-26 15:13 ` Ross Burton [this message]
2026-06-26 15:13 ` [PATCH 3/3] classes/gtk-doc: inherit python3native only if gtk-doc is enabled Ross Burton
2026-06-28 15:03 ` [OE-core] [PATCH 1/3] blueprint-compiler: inherit python3-dir not python3targetconfig Mathieu Dubois-Briand
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=20260626151325.1735368-2-ross.burton@arm.com \
--to=ross.burton@arm.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