Feature added by: Cristian Morales Vega (RedDwarf) Feature #309683, revision 1 Title: Integrate "ABI compliance checker" in the Build Service Requested by: Cristian Morales Vega (reddwarf) Partner organization: openSUSE.org Description: Integrate the "ABI compliance checker"* software as a (rpmlint?) post check in the Build Service. ABI compliance checker, as it name implies, checks for changes in a library that could break its backwards compatibility. The check probably should be done only if the soname didn't changed between two rebuilds. A way to detect this is needed. Also the last check would need to be stored somewhere permanently so an extra automatic rebuild doesn't deletes the info before the packager has time to see it. It seems to only output HTML. Not bad for the Build Service WebUI, but perhaps the software itself will need to be modified to be able to output something more osc friendly. * http://ispras.linux-foundation.org/index.php/ABI_compliance_checker Business case (Partner benefit): openSUSE.org: Maintain backward compatibility in a library is error prone. A packager doesn't always (most of the time?) has a deep understanding of such library, so we end just trusting upstream. Unfortunately you can't always trust upstream (https://bugzilla.novell.com/609249). Even if we rebuild everything for the official packages, this is still a problem for interaction between packages of different repos (e.g. mkvtoolnix from multimedia:apps needs libebml 0.8.0 from multimedia:libs, but VLC from Packman is compiled against libebml 0.7.8 from the official repo... libebml 0.7.8 and 0.8.0 have the same soname but are binary incompatible). -- openSUSE Feature: https://features.opensuse.org/309683