new upstream tracker (

Garrett Cooper yanefbsd at
Sat May 22 19:30:28 UTC 2010

On Sat, May 22, 2010 at 4:54 AM, Andrey Ponomarenko <susanin at> 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.

    Just out of curiosity, is this a system for monitoring the 3rd
party libraries that have been imported into our base system, or is it
a generic tool for running testcases? I'll poke at it further, in the
meantime, but it would be helpful if an expert could comment on the
issue more :).
    I ask because Linux in and of itself doesn't really have a base
system and everything's packages from the get-go, whereas *BSD has a
userland with some 3rd party packages all wrapped into one base
    Also, how do you `test' the applications -- using the runtime
tests produced in previous versions, or by just executing applications
and observing whether or not the API calls pass or fail?

More information about the freebsd-ports mailing list