new upstream tracker (linuxtesting.org)
susanin at ispras.ru
Tue May 25 06:38:39 UTC 2010
On 05/22/2010 05:21 PM, Kostik Belousov wrote:
> On Sat, May 22, 2010 at 05:12:10PM +0400, Andrey Ponomarenko wrote:
>> On 05/22/2010 04:30 PM, Kostik Belousov wrote:
>>> On Sat, May 22, 2010 at 03:54:20PM +0400, Andrey Ponomarenko wrote:
>>>> Hello, I'm from ISPRAS and we have created an experimental system for
>>>> monitoring and analyzing of upstream libraries development. It may be
>>>> helpful for analyzing risks of updating one of the distribution
>>>> components (shared libraries). The web page of upstream-tracker is:
>>>> It now includes ABI changes analysis and API shallow test results for
>>>> several versions of 60 popular open source libraries.
>>>> Any bugs or feature requests are welcome. Thanks.
>>> WOW. Can you, please, share the setup of the tracker ?
>> The tool itself is very young and is not well documented yet. Although
>> the first version has been recently released under dual GNU GPL and LGPL
>> We are not recommended to use this version of the tool by yourself. Very
>> soon we will release 1.1 version containing a lot of bug fixes and new
>>> It would be amazingly interesting if you added FreeBSD base system
>>> libraries to the tracker.
>> Provide, please, the list of necessary libraries.
> Having libc.so, libthr.so, libm.so, libgcc_s.so, libstdc++.so, libz.so
> from the specified versions under the monitor would be very nice start.
I know libc.so and libm.so are from GLIBC library, libgcc_s.so and
libstdc++.so are from GCC.
Where can I find sources of libthr.so? The entry point for the library
in the tracker is the package with source code or at least repository
libz.so is already added at
> The ABI definition for the base system is currently under discussion,
> we may provide more authoritative list for the libraries that would
> be useful to monitor.
You are welcome. References to the source code of libraries will be very
> Also, I suppose the project may put together some resources to set up
> the local tracker. If you are interested in helping us with this,
> I will proceed further.
Upstream-Tracker is built on top of two basic components:
ABI-Compliance-Checker and API-Sanity-Autotest. For creating of your
local tracker the ABI-Compliance-Checker tool may be used. It is a tool
for checking two particular versions of a library for ABI compliance:
This tool is well tested and documented.
>>> It would be extremely interesting and
>>> useful for us to see changes among releases and tips of the
>>> stable and head branches.
>> Andrey Ponomarenko
>> Linux Verification Center, ISPRAS
>> web: http://www.linuxtesting.org
Linux Verification Center, ISPRAS
More information about the freebsd-ports