How do you think about to describe data around the requirements of ABIs and APIs for various software libraries and their users a bit more explicitly (instead of encoding such information often in a main version number)?
This is already being practised in case you have not noticed.
Do you know any more software developments (besides the packages "libabigail-tools" and "abi-compliance-checker") which can improve the handling for the combination of the properties "application binary interface" and "application programming interface" to some degree? Will any advanced queries on the package database help to clarify special cases for some software dependencies? Are you also looking for further ideas to achieve safer and more convenient solutions? Regards, Markus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org