On Fri, 7 Jan 2022 14:02, Thorsten Kukuk <kukuk@...> wrote:
On Fri, Jan 07, Jan Engelhardt wrote:
On Friday 2022-01-07 10:47, Stefan Seyfried wrote:
And yes, I tell them daily to go away and kill themselves when they come around with on their SLES12 installations, that would be simply go away if they switched to SLES15+. Or when they whine about their sles15 problems that come from them using SP1 instead of SP3+updates.
So yes, paying customers really like old stuff :-)
Or you just did not sell it well enough.
Maintenance costs for an aging car rise to the point where getting a new one is more economical. At this very price-parity point, one would surely pick the one that looks nicer.
This is true for the average consumer, but not for data centers. Very often they run into a sitution, where updating all server would be much more expensive then an exorbitant price for maintaining the old code base. Often it is the sheer mass on virtual machines and the missing knowledge about the running workload which prevents them from updating.
Thorsten
May I propose a longterm solution? 1. No distro-shipped python program refers to /usr/bin/python at all, but to /usr/bin/python{version} instead, no hassel with /usr/bin/python. 2. /usr/bin/python is managed by (lib-)alternatives (or similar), for: 2.a: SLE-14.(0..4) this points to /usr/bin/python3.6 2.b: Leap14.4 this point to /usr/bin/python{latest stable} for SLE-15 imho this should not point to a version lower than 3.10 yes, this will lead to recompile of ALL distro included python-stuff, but much less hassel, version-related anger and frustation in the long run. Dislaimer: I'm no expert at python at all, please do not take this proposal as word-of-god, insult to you, or similar, but just as an idea for a longterm way out of this mess. - Yamaban.