<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Dec 26, 2013 at 8:51 PM, Adam Williamson <span dir="ltr"><<a href="mailto:awilliam@redhat.com" target="_blank">awilliam@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Time for another PSA...<br>
<br>
It appears libevdev 0.6 breaks the library's ABI without bumping the<br>
soname (and without an announcement here or anywhere else I can find,<br>
but an ABI change without an soname bump is just flat out wrong whether<br>
announced or not). 0.6 was sent to Rawhide, F19 and F20 simultaneously.<br></blockquote><div><br></div><div>I've been maintaining abi-compliance-checker in Fedora for some time now. Is there a good way to integrate it into the build system so that it would run a diff with the previously released package to check for breakages? It could be treated as informative, not necessarily a failure. It produces a fairly easy to read html report.</div>
<div><br></div><div>I already use it manually to check for abi breakages in packages where upstream doesn't maintain good API/ABI versioning. <br></div><div><br></div><div>I maintain pkgdiff as well and it's pretty cool but only checks diffs between packages and can do it just using the debuginfo package of the two releases.</div>
<div><br></div><div>Richard</div></div></div></div>