From: Markus Volk <f_l_k@t-online.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: "Sajal, Sakib" <Sakib.Sajal@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] blktrace: ask for python3 specifically
Date: Thu, 17 Nov 2022 15:49:52 +0100 [thread overview]
Message-ID: <4JYHLR.TSDICAGWLD7L@t-online.de> (raw)
In-Reply-To: <CANNYZj-mNkCgk=XHWBvqpqr=x4R9AMyktBTj49p-QK=Ui2whxg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
Am Do, 17. Nov 2022 um 08:43:15 +0100 schrieb Alexander Kanavin
<alex.kanavin@gmail.com>:
> Yes, they kinda have a point. Referring to latest python as python3
> forever is silly. Unfortunately we have all those users with legacy
> proprietary python2 things, and they feel like they still 'own'
> python (without a number).
To avoid patching dozens of scripts, i use this bbappend for python3
until the time comes to make it the default:
do_install:append:class-target() {
ln -sf ${bindir}/python3 ${D}${bindir}/python
}
FILES:${PN}:class-target += "${bindir}/python"
[-- Attachment #2: Type: text/html, Size: 826 bytes --]
next prev parent reply other threads:[~2022-11-17 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 18:33 [PATCH] blktrace: ask for python3 specifically Sakib Sajal
2022-11-03 19:00 ` [OE-core] " Alexander Kanavin
2022-11-16 22:01 ` Sajal, Sakib
2022-11-17 7:43 ` Alexander Kanavin
2022-11-17 14:49 ` Markus Volk [this message]
2022-11-17 15:49 ` Alexander Kanavin
2022-11-17 16:09 ` Markus Volk
2022-11-18 12:20 ` Markus Volk
2022-11-18 12:36 ` Alexander Kanavin
2022-11-18 13:20 ` Markus Volk
2022-11-19 17:37 ` Alexander Kanavin
2022-11-20 17:55 ` Markus Volk
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=4JYHLR.TSDICAGWLD7L@t-online.de \
--to=f_l_k@t-online.de \
--cc=Sakib.Sajal@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