Our Open Source Collection provides pre-compiled binaries in the native package manager format or as RPM packages for the following platforms:

• AIX 5.2, 5.3, 6.1, 7.1, 7.2
• HP-UX 11.23/PA, 11.23/IA, 11.31/PA, 11.31/IA
• Redhat Enterprise Linux 5/x86, 5/x86-64, 6/x86, 7/86-64, 8/x86-64, 9/x86-64
• Solaris 10/SPARC, 10/x86, 11/SPARC, 11/x86

Binaries are built to a standard path, "/opt/TWWfsw/package", with each package installed to a separate directory. Because each package is installed to a separate directory, multiple versions of a package can coexist. After a package has been installed, a postinstall script runs to create symbolic links in a common directory for binaries, GNU info pages, and man pages. As new packages are installed, the postinstall scripts replace links to older versions of the program and upgrade configuration files from older versions to the new version.

In addition to pre-compiled binaries, source code to all packages, instructions on how each software package was compiled, and instructions on how each binary package was created is included. The tools used to build the software and binary packages is also included (cf. sbutils and pbutils) in addition to a cross-platform package installation tool to make package installation and removal consistent across platforms.

Releases are purchased annually which provides updates throughout the year, patches, and security fixes between releases. Our release roadmap contains the shipping dates for upcoming releases. patches, or security fixes between releases.

While pre-compiled binaries are available from other sites, our Open Source Collection offers the following advantages:

1. Packages are built to automatically install common binaries, info pages, and man pages in a common area.
2. Packages are installed to the same location on all platforms; package versions are consistent across platforms. This increases the uniformity in your environment.
3. We keep abreast of new patches available for the packages we support and newly-released packages.
4. Packages are compiled, where possible, with the vendor C and C++ compilers.
5. Dependencies included in packages.
6. Because the installation path is "/opt/TWWfsw/package", multiple versions can coexist.
7. Package upgrades are handled smoothly through intelligent postinstall scripts.
8. Configuration files for previous versions are saved when upgrading to a newer release.
9. Detailed package notes and changelog information.
10. Cross-platform installation tool.
11. Instructions on how each software package was created and on how each binary package was created.

If our standard installation path does not suit your environment, please contact us for information about a custom build of the packages we provide. A custom build is the preferred choice if our default installation prefix must be changed or if packages must be compiled with different options.