Please can anyone tell me (or point me to information about) binary compatibility between Leap minor versions. What is the intention (or otherwise) for binary compatibility between minor versions.
Specifically if I build my application for 15.1 should I expect those binaries to run on 15.2 (and eventually 15.3)??
I’m finding that my application will not run on 15.2 because the version of libicu has changed significantly.
Is the only option to build my application for 15.2 also?
Thanks.
Hi
Yes, Leap 15.1 is EOL and not supported.
Thanks for the reply, but out of interest assuming that 15.1 was not EOL is there any expectation that minor versions of Leap (15.0,15.1,etc…) should be binary compatible? So that an application built for 15.1 should run on 15.2 or not.
Hi
Yes and no… all depends on what it’s using and if libs have been bumped for whatever reason.
I see 60_2 (Dec 2017) in Leap 15.1 and 65.1 (Oct 2019) in Leap 15.2;
Changelog: File icu.changes of Package icu - openSUSE Build Service
It isn’t really binary compatibility. What matters is library compatibility. If the application is statically linked, then only binary compatibility matters. With dynamic linking, library compatibility matters.
Please note, however, that I am not arguing for static linking. There are good reasons for using dynamic linking.
And an additional note. I have a program that I use, which was last compiled in 2006. I was running SuSE 10.1 at that time. And it still works, though I do need to install “glibc-32bit” for it to work. Evidently it only uses simple library interfaces that still are working as before.