DevHeads.net

Postings by Ponomarenko Andrey

API changes report for MySQL Connector/J

Hi,

I'd like to share report on API changes and backward compatibility for the MySQL Connector/J library: <a href="https://abi-laboratory.pro/java/tracker/timeline/mysql-connector-java/" title="https://abi-laboratory.pro/java/tracker/timeline/mysql-connector-java/">https://abi-laboratory.pro/java/tracker/timeline/mysql-connector-java/</a>

BC — binary compatibility
SC — source compatibility

The report is generated by the <a href="https://github.com/lvc/japi-tracker" title="https://github.com/lvc/japi-tracker">https://github.com/lvc/japi-tracker</a> tool for jars at <a href="http://central.maven.org/maven2/mysql/mysql-connector-java/" title="http://central.maven.org/maven2/mysql/mysql-connector-java/">http://central.maven.org/maven2/mysql/mysql-connector-java/</a>. The tool checks for API changes according to the article <a href="https://wiki.eclipse.org/Evolving_Java-based_APIs_2" title="https://wiki.eclipse.org/Evolving_Java-based_APIs_2">https://wiki.eclipse.org/Evolving_Java-based_APIs_2</a>.

Hope it will be helpful for users and maintainers of the library.

Thank you.

ABI changes analysis for the Linux kernel

Hello,

This is a tracker of ABI changes in the new upstream releases of the Linux kernel (defconfig, x86_64): <a href="https://abi-laboratory.pro/tracker/timeline/linux/" title="https://abi-laboratory.pro/tracker/timeline/linux/">https://abi-laboratory.pro/tracker/timeline/linux/</a>

The tracker performs backward binary compatibility analysis of all public exported symbols and data types (declared in the ".ksymtab" and ".ksymtab_gpl" sections of the vmlinux binary + system calls) and lists all added/removed symbols.

The source code of the tool is published on github: <a href="https://github.com/lvc/kernel-abi-tracker" title="https://github.com/lvc/kernel-abi-tracker">https://github.com/lvc/kernel-abi-tracker</a>

The tool can be used to analyze downstream kernels as well. See README of the project.

A new tool for backward compatibility analysis of API/ABI interfaces in RPM packages

Hello,

I'd like to present a new free tool for maintainers of software libraries — Package ABI Diff Tool (pkg-abidiff). It's a tool for backward compatibility analysis of API/ABI interfaces in RPM packages. The tool is based on ABI Compliance Checker and ABI Dumper tools.

The tool does the following:

1. Extracts input packages
2. Searches for *.debug, *.so and header files
3. Creates ABI dumps of all found shared objects
4. Filters out private part of the ABI using info from header files
5. Matches shared objects in old and new packages
6.

A new tool for backward compatibility analysis of API/ABI interfaces in RPM packages

Hello,

I'd like to present a new free tool for maintainers of software libraries — Package ABI Diff Tool (Pkg-ABIdiff). It's a tool for backward compatibility analysis of API/ABI interfaces in RPM packages. It is based on ABICC and ABI Dumper tools.

The tool does the following:

1. Extracts input packages
2. Searches for *.debuginfo, *.so and header files
3. Creates ABI dumps of all found shared objects
4. Filters out private part of the ABI using info from header files
5. Matches shared objects in old and new packages
6.

Linux Kernel ABI report

Hello,

I continued to maintain ABI report for the Linux kernel here: <a href="http://abi-laboratory.pro/tracker/timeline/linux/" title="http://abi-laboratory.pro/tracker/timeline/linux/">http://abi-laboratory.pro/tracker/timeline/linux/</a>

The report represents history of ABI changes since 2.6.36 up to 4.4.5 version of the kernel. It is now generated by the ABI tracker, ABI monitor, ABI dumper and ABI compliance checker tools. All of them are open-source and shared on github: <a href="https://github.com/lvc" title="https://github.com/lvc">https://github.com/lvc</a>

Unlike the previous version the new tracker checks only public ABI symbols exported by the Linux kernel, i.e. declared in the ksymtab/ksymtab_gpl binary sections + system calls.

Linux Kernel ABI report

Hello,

I continued to maintain ABI report for the Linux kernel: <a href="http://abi-laboratory.pro/tracker/timeline/linux/" title="http://abi-laboratory.pro/tracker/timeline/linux/">http://abi-laboratory.pro/tracker/timeline/linux/</a>

The report represents history of ABI changes since 2.6.36 up to 4.4.5 version of the kernel. It is now generated by the ABI tracker, ABI monitor, ABI dumper and ABI compliance checker tools. All of them are open-source and shared on github: <a href="https://github.com/lvc" title="https://github.com/lvc">https://github.com/lvc</a>

Unlike the previous version the new tracker checks only public ABI symbols exported by the Linux kernel, i.e. declared in the ksymtab/ksymtab_gpl binary sections + system calls.

API/ABI tracker

Hello,

I've started to maintain ABI changes report for the libruby here: <a href="http://abi-laboratory.pro/tracker/timeline/ruby/" title="http://abi-laboratory.pro/tracker/timeline/ruby/">http://abi-laboratory.pro/tracker/timeline/ruby/</a>

Hope the report will help Linux maintainers of the library to be aware of ABI structure changes, added/removed symbols and SONAME bumps.

Thank you.

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

Future of the Linux upstream tracker

Hello,

Some of you may have noticed that the service for analysis of ABI changes in Linux libraries is not available any more: <a href="http://upstream-tracker.org/" title="http://upstream-tracker.org/">http://upstream-tracker.org/</a>

The archive from 21 July 2015 is still available and supported by ROSA team: <a href="http://upstream.rosalinux.ru/" title="http://upstream.rosalinux.ru/">http://upstream.rosalinux.ru/</a>

But ... Good news everyone! I've spent about a half-year to implement an open-source alternative of the tool from scratch and I'm glad to inform you that it's finally ready and available at: <a href="https://github.com/lvc/abi-tracker" title="https://github.com/lvc/abi-tracker">https://github.com/lvc/abi-tracker</a>

So everyone can set up their own ABI tracker for the interested libraries.