GT.M Integration

We pushed out the 0.8.8 release today because there are a number of bug fixes that we think warrant a release.  Some of these (like the package dependency issue and the Mailman issue) were already addressed by packages we uploaded to the repository after the 0.8.7 release, but others (like the routine compilation issue and the $PATH issue) were in the utilities themselves.  Note that the $PATH bug has the potential to prevent backups from completing, but only if you're running more than one OpenVista instance on the same machine, and only if those instances are using different versions of GT.M.

The new release also includes the recently-released GT.M V5.4-000 and supports the upcoming Ubuntu 10.04 Long-Term Support (LTS) release, codenamed Lucid Lynx.

The KIDS build was not updated for this release.

As with the previous 0.8.7 release, grab the new packages from the yum or apt repository.

Packages for the upcoming long-term support release of Ubuntu, version 10.04 (Lucid), have been uploaded to the apt repository.  Lucid is currently in Alpha 2, but we'll continue to monitor it and upload new packages as necessary. 

Note that although we're building for Lucid now, no active testing is happening, so if you're using Lucid, please test and report any issues you find!

There were two main changes in this release.

• Ubuntu 9.10 (Karmic) is now supported, and we've moved to yum and apt repositories to take the guesswork out of which package should be installed.  With CentOS 5, Ubuntu 9.04 (Jaunty) and Ubuntu 9.10 (Karmic), and multiple versions of GT.M on each, the downloads page was becoming very long and confusing.  We now also compile and release for both architectures -- i386 and x86_64/amd64.  Just follow the links on the downloads page to the correct repository page for your distribution (yum repository for CentOS and apt repository for Ubuntu), add the repository to your sources, and use yum or apt to automatically install all the packages and their dependencies.
• You can now override $gtm_dist, $gtmroutines, and $gtmgbldir on a per-instance basis by setting them in an env file.  The file lives in the etc subdirectory of an OpenVista instance.  Practically speaking, the only variable you would likely override is the $gtmroutines variable, to support things like routine tiers or to share routines across instances.  Note that if you override $gtmroutines or $gtmgbldir to point to routines, global directory files, or database files outside their normal directories (the routines and globals directories), you must back them up yourself.  ovbackup will follow symlinks when backing up files, but it will not back up files outside of the normal directories, regardless of your settings in the env file.  The env file itself has lots of comments explaining various strategies for setting these variables.  We recommend leaving these variables at their defaults in production environments. 

In addition, there were a handful of smaller updates -- fixes for interfaces, saving routines, switching UCIs, and the null device, minor enhancements to ovimport, ovrestore, and ovbackup, and a new ovcheckperms utility.