From: Denys Dmytriyenko <denis@denix.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Jiaying.Song.CN@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [scarthgap][master][PATCH] python3: provide /usr/bin/python as a symlink to python3
Date: Fri, 19 Jul 2024 12:46:39 -0400 [thread overview]
Message-ID: <20240719164639.GN17572@denix.org> (raw)
In-Reply-To: <CANNYZj_6miWR2kz3qQpMNFEtNQM6v1iwr6ia9a-=T5hTUje92g@mail.gmail.com>
On Fri, Jul 19, 2024 at 08:18:26AM +0200, Alexander Kanavin wrote:
> There was a proposal with two option (maybe that was missed) and I
Yeah, I guess I missed that one.
> suggested just adding the link and be done with it. We can drop lots of
> patches and send tweaks then.
>
> Alex
>
> On Fri 19. Jul 2024 at 8.17, Alexander Kanavin <alex.kanavin@gmail.com>
> wrote:
>
> > But there is no alternative. Python is python3 and has been for years.
Understood, but many distros still manage symlinks via update-alternatives,
hence my question. I guess since we don't supoort multiple versions at the
same time, it does make sense to keep it simple...
> > Alex
> >
> > On Fri 19. Jul 2024 at 0.47, Denys Dmytriyenko <denis@denix.org> wrote:
> >
> >> Should this be done via update-alternatives, like many other Linux
> >> distros do?
> >>
> >>
> >> On Wed, Jul 17, 2024 at 10:32:01AM +0800, Song, Jiaying (CN) via
> >> lists.openembedded.org wrote:
> >> > From: Jiaying Song <jiaying.song.cn@windriver.com>
> >> >
> >> > The /usr/bin/python cannot find the correct Python interpreter, so a
> >> symbolic
> >> > link is added to point it to the Python3 interpreter.
> >> >
> >> > Signed-off-by: Jiaying Song <jiaying.song.cn@windriver.com>
> >> > ---
> >> > meta/recipes-devtools/python/python3/python3-manifest.json | 1 +
> >> > meta/recipes-devtools/python/python3_3.12.4.bb | 1 +
> >> > 2 files changed, 2 insertions(+)
> >> >
> >> > diff --git a/meta/recipes-devtools/python/python3/python3-manifest.json
> >> b/meta/recipes-devtools/python/python3/python3-manifest.json
> >> > index 46092d4004..f9259e1450 100644
> >> > --- a/meta/recipes-devtools/python/python3/python3-manifest.json
> >> > +++ b/meta/recipes-devtools/python/python3/python3-manifest.json
> >> > @@ -220,6 +220,7 @@
> >> > "files": [
> >> > "${bindir}/python${PYTHON_MAJMIN}",
> >> > "${bindir}/python${PYTHON_MAJMIN}.real",
> >> > + "${bindir}/python",
> >> > "${bindir}/python3",
> >> > "${includedir}/python${PYTHON_MAJMIN}/pyconfig*.h",
> >> > "${libdir}/python${PYTHON_MAJMIN}/UserDict.py",
> >> > diff --git a/meta/recipes-devtools/python/python3_3.12.4.bb
> >> b/meta/recipes-devtools/python/python3_3.12.4.bb
> >> > index 743ba0b1f1..94535e7678 100644
> >> > --- a/meta/recipes-devtools/python/python3_3.12.4.bb
> >> > +++ b/meta/recipes-devtools/python/python3_3.12.4.bb
> >> > @@ -165,6 +165,7 @@ do_install:prepend() {
> >> >
> >> > do_install:append:class-target() {
> >> > oe_multilib_header python${PYTHON_MAJMIN}/pyconfig.h
> >> > + ln -sf ${bindir}/python3 ${D}${bindir}/python
> >> > }
> >> >
> >> > do_install:append:class-native() {
> >> > --
> >> > 2.44.0
> >>
> >
next prev parent reply other threads:[~2024-07-19 16:46 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 [this message]
2024-07-23 13:38 ` Konrad Weihmann
2024-07-23 16:44 ` [OE-core] " 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=20240719164639.GN17572@denix.org \
--to=denis@denix.org \
--cc=Jiaying.Song.CN@windriver.com \
--cc=alex.kanavin@gmail.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