On Tue, Feb 16, L A Walsh wrote:
This is another example of a snapshot that will
upgrades impossible w/o a full rebuild -- for a similar reason
rpm 4.15 can't be built by rpm 4.14 or before. rpm 4.11 ships
with rpmlibs-v3, while rpm4.15 ships rpmlibs-v9. The libs
jumped 6 versions while rpm went up 0.14.
The windows of what binaries work with what date of TW
is too small.
Is suse supporting this model for enterprise customers? I can't
believe they would tolerate it.
Seems you mix up Tumbleweed as rolling release distribution with
openSUSE Leap/SLE as stable distribution.
In the first case, you have always the newest stuff, in the later
case, you have stable interfaces, with the drawback, this is old
Tumbleweed tries the best to provide all the new, shiny features
in a stable way, Leap and SLE tries eveything to stay compatible
without providing all the new features.
It used to be (before all binaries had version
in their binary), that you could upgrade across versions for
most things, or install multiple versions of some libraries
for various programs.
You can do that still today. If a library does not use symbol
versioning and changes incompatible without changing the soname,
it's a bug.
Glibc seems to support only a buggy API such that
can't be used on the same machine as linked by file-name.
If you would understand a little bit about how starting ELF binaries
works, it would be pretty clear that you can have only one ld.so,
and thus only one version of glibc.
Which itself is already incorrect, you can install multiple versions
of glibc in parallel, but that's really not easy and you don't want
that as normal user.
And: everything compiled against glibc 2.x still works with glibc 2.33
today. The glibc developers are doing really a great job in keeping
the ABI stable. There is absolute no need to keep older glibc versions
While some may think I have uniq problems, the
are going to have more and more of these cases. It's not a workable
Maybe Leap would be the right distro for you?
Also if you need applications with different libraries than your current system you can
- a VM
> > I can take programs in Win from 10-20 years ago and they still work
> > on a current day win because the OS loads library updates by version.
> > Unix did the same -- but move to linux, and vendors got lazy and stopped
> > using the correct versions to link with. Why? And how can this be fixed?
> ??? Where did Linux stopped using the correct version to link with?
> All libraries with a public interface have a soname and many of them even
> symbol versioning. Else see above.
> Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS
> SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
> Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg)