Il giorno mer 5 giu 2019 alle ore 17:19 Nir Soffer <nsoffer@redhat.com> ha scritto:
In several projects (e.g. vdsm, imageio, sanlock), we have the issue of building python 3 packages for Fedora.
The current build process create packages with the same name for both python 2 and python 3. When the packages are published to oVirt repository, the python 3 packages overwrite the python 2 packages.
We can rename the packages properly (e.g. python2-xxx, python3-xxx) but this requires lot of work and typically breaks later in the code publishing the packages.
There is also the difficulty of building both python 2 and python 3 packages from same spec in the same build. This should be possible but not easy.
Since python 2 is about to die soon, should we simplify by building python 2 *or* python 3, depending on version?
Fedora 29: python 2.7 Fedora 30: python 3.7 CentOS 7: python 2.7 CentOS 8: python 3.6
I'm totally in agreement with this, +100 let's build for a single python version per distribution and above mapping looks perfect to me.
This make it possible to test and develop on python 2.7 until vdsm is fully functional on python 3, and it save resources in the CI.
Thoughts?
Nir
-- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@redhat.com <https://red.ht/sig> <https://redhat.com/summit>