Am 13.07.22 um 15:23 schrieb Dan Čermák:
Hi Axel,
Axel Braun <docb@opensuse.org> writes:
Hi Lubos,
Am Dienstag, 12. Juli 2022, 15:33:18 CEST schrieb Lubos Kocman:
Sticking with old/unsupported python and ruby was a pain as it became virtually impossible to update some community packages. I have some good news!
We can't change the default "system python" for code-stream 15, so we've agreed to a plan to offer a parallel python 3.10+ full-stack in 15 SP5. There is a request to add 3.11 interpret to SP5, so perhaps we should consider that version instead. Essentially we have the same scenario for ruby 2.7, where we plan to re-build all rubygems also for 2.7. This is indeed a good step forward. As I understood that the base system will still deliver python 3.6 and ruby 2.7 as standard - and this should not change - we need to enable the build of
I would expect that there is a similar mechanism for python.
Most python specfiles are single-spec multiflavor already. I think you only need to expand the global buildset for the python flavors in the prjconf to %pythons %{?!skip_python310:python310} %{?!skip_python3:python3} That way you will have python310-foo packages in addition to the python3-foo packages for python 3.6. Any package where you need an updated version in the python 3.10 sitelib but can't update Python 3.6, you just add another package which has anything like %if 0%{?suse_version} <= 1500 %define skip_python3 1 %endif Of course the skip_python3 definition should not be there for Tumbleweed build targets, as that would mean no flavor at all. - Ben