Date: Sat, 22 May 2010 12:30:25 -0700 From: Garrett Cooper <yanefbsd@gmail.com> To: Andrey Ponomarenko <susanin@ispras.ru> Cc: ports@freebsd.org Subject: Re: new upstream tracker (linuxtesting.org) Message-ID: <AANLkTikxaIA6QvHAkw5HtAY81nQzlJzcB008HfMR0mny@mail.gmail.com> In-Reply-To: <4BF7C5EC.20500@ispras.ru> References: <4BF7C5EC.20500@ispras.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 22, 2010 at 4:54 AM, Andrey Ponomarenko <susanin@ispras.ru> 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: > http://linuxtesting.org/upstream-tracker/ > 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 system. 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? Thanks! -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikxaIA6QvHAkw5HtAY81nQzlJzcB008HfMR0mny>