I also vote against it.

I'm on the fence but I'll be swayed by the "against" voters.

There are pros and cons to a system-wide solution but it seems that
people prefer to have these problems fixed in each affected recipe.
Best solution is to update the script to call and work with python3.
If the upstream refuses to do that, the layer would have to carry a patch.

This is how most such '/usr/bin/python' problems have been solved.
It's a shame that upstream python didn't mandate a specific solution.

Btw, some people could use:

https://github.com/Igalia/meta-webkit/blob/main/recipes-devtools/python/python-is-python3_1.0.bb
https://github.com/Igalia/meta-webkit/commit/b2156c282a6e727100dee25155fbc38d1532b573
https://github.com/Igalia/meta-webkit/commit/46fbfbc58f82abc3dc8794c630172d4554be0830

❯ git log --stat 46fbfbc5
commit 46fbfbc58f82abc3dc8794c630172d4554be0830
Author: Carlos Alberto Lopez Perez <clopez@igalia.com>
Date:   Mon Dec 19 20:29:05 2022

    Add a new image and distro definition for using on the WebKit CI for WPE perf bots
    
 ...

    * It adds also a 'python-is-python3' recipe that creates a symlink
    to provide the unversioned python interpreter as python3.

but both oe-core and meta-oe maintainers said on today's YP tech call that
they would *not* carry that recipe.

../Randy

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
 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#202364): https://lists.openembedded.org/g/openembedded-core/message/202364
Mute This Topic: https://lists.openembedded.org/mt/107264938/3616765
Group Owner: openembedded-core+owner@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [randy.macleod@windriver.com]
-=-=-=-=-=-=-=-=-=-=-=-

-- 
# Randy MacLeod
# Wind River Linux