From: "Konrad Weihmann" <kweihmann@outlook.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [scarthgap][master][PATCH] python3: provide /usr/bin/python as a symlink to python3
Date: Tue, 23 Jul 2024 06:38:38 -0700 [thread overview]
Message-ID: <15389.1721741918254132393@lists.openembedded.org> (raw)
In-Reply-To: <20240719164639.GN17572@denix.org>
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
I also vote against it.
While I see the convenience in dropping a lot of patches the better approach would be to add something like python-is-python3, for the ones that require it.
(meta-webkit does provide it already https://github.com/Igalia/meta-webkit/blob/main/recipes-devtools/python/python-is-python3_1.0.bb ).
Adding a link by the base package and recommending to the user to remove it again, would create two very unwelcome situations.
a) it will clash at image assembly with an error message that will no easily point to the python base package
b) create a need to run with a permanent remove operation on top of poky (creating the need for new sstate cache artifacts)
What I could see is to move the symlink into an optional package, which could be used by the few recipes that still use the "wrong" interpreter line via RDEPENDS, that would be the much cleaner solution here
[-- Attachment #2: Type: text/html, Size: 1113 bytes --]
next prev parent reply other threads:[~2024-07-23 13:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 2:32 [scarthgap][master][PATCH] python3: provide /usr/bin/python as a symlink to python3 jiaying.song.cn
2024-07-18 22:47 ` [OE-core] " Denys Dmytriyenko
2024-07-19 6:17 ` Alexander Kanavin
2024-07-19 6:18 ` Alexander Kanavin
2024-07-19 16:46 ` Denys Dmytriyenko
2024-07-23 13:38 ` Konrad Weihmann [this message]
2024-07-23 16:44 ` Randy MacLeod
2024-07-23 17:56 ` Alexander Kanavin
2024-07-23 18:18 ` Konrad Weihmann
2024-07-23 18:25 ` Alexander Kanavin
2024-07-23 18:41 ` Randy MacLeod
2024-07-24 16:01 ` Richard Purdie
2024-07-24 16:17 ` Alexander Kanavin
2024-07-24 16:36 ` Martin Jansa
2024-07-24 16:44 ` 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=15389.1721741918254132393@lists.openembedded.org \
--to=kweihmann@outlook.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