--- web/www/libstatgrab/index.xhtml 2005/07/31 08:39:35 1.40 +++ web/www/libstatgrab/index.xhtml 2007/07/13 21:56:52 1.48 @@ -41,6 +41,7 @@ +

What is libstatgrab?

@@ -80,6 +81,46 @@ freshmeat?

+ Saturday 14 July 2007 +

+

+ Version 0.15 of libstatgrab has been released.
+ Download it from one of our mirrors. +

+

+ This release fixes a regression introduced on OpenBSD in + the last release - memory statistics were reported + incorrectly. Some other minor changes have been made, see + the NEWS file for more information. +

+

+ Monday 8 January 2007 +

+

+ Version 0.14 of libstatgrab has been released.
+ Download it from one of our mirrors. +

+

+ This release contains mainly bugfixes - see the NEWS file + in the distribution for a full list. It also brings a new + feature in saidar: colour support, which can be activated + with the -c runtime flag. +

+

+ Monday 20 March 2006 +

+

+ Version 0.13 of libstatgrab has been released.
+ Download it from one of our mirrors. +

+

+ This release mainly includes a bunch of bug fixes, but + also brings preliminary support for WIN32. We've also + added a few lines to the header file to make C++ linking + easier. Please see the NEWS file in the distribution for + full details. +

+

Sunday 31 July 2005

@@ -216,7 +257,7 @@

pystatgrab, a new package containing a set of Python - bindings, has been released. Check out it's + bindings, has been released. Check out its project page.

@@ -250,7 +291,7 @@ Here are links to bindings for higher level languages that provide access to libstatgrab. If you've written a binding for another language, please get - in touch so we + in touch so we can add a link here.

@@ -261,17 +302,23 @@ FreeBSD
  • - Gentoo Linux + Gentoo Linux
  • Solaris (Blastwave)
  • + Solaris (SunFreeware) +
  • +
  • Debian
  • NetBSD
  • +
  • + RPMs for various Linux distributions +
  • These are various pre-packaged versions of libstatgrab @@ -308,50 +355,67 @@

    The only online documentation we have at the moment is the - manual pages converted in to HTML format. It's probably - best to start with the overview manual page: + manual pages converted in to HTML format. First are the + manual pages for the command line tools:

    + We also have an overview page for the library: +

    + +

    Then we have the manual pages for each function: