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:

Packages are built to automatically install common
binaries, info pages, and man pages in a common area.

Packages are installed to the same location on all
platforms; package versions are consistent across platforms. This
increases the uniformity in your environment.

We keep abreast of new patches available for the
packages we support and newly-released packages.

Packages are compiled, where possible, with the vendor
C and C++ compilers.

Dependencies included in packages.

Because the installation path is
"/opt/TWWfsw/package", multiple versions can
coexist.

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.