Resources Downloads Account Logout Contact
 
Package Internals
Installation Directories
 

Packages are installed to the following directories:
/opt/TWWfsw/package Binaries, libraries, documentation, man pages, GNU info pages.
/etc/opt/TWWfsw/package Local configuration files. Files in this directory are intended to be host-specific, such as configuration files for the Apache HTTPD web server, NTP server, and Postfix mail server
/var/opt/TWWfsw/package Local log files. Files in this directory are host-specific log files and runtime state files created by daemons such as the Apache HTTPD web server, NTP server, and Postfix mail server.
/etc/dt CDE startup files for window managers like FVWM, GNOME, and KDE.
/etc/init.d Daemon startup scripts for IRIX, Redhat Linux, and Solaris. The name of the startup script mirrors the package name.
/sbin/init.d Daemon startup scripts for HP-UX and Tru64 UNIX. The name of the startup script mirrors the package name.
/etc/rc.d Daemon startup scripts for AIX. The name of the startup script mirrors the package name.

Under the main installation directory, "/opt/TWWfsw", several package names have special significance:
/opt/TWWfsw/packagep Our distribution of programs such as Perl, Python, Ruby, and Tcl included both the main program and certain 3rd-party modules. Rather that combining both the program and 3rd-party modules under "/opt/TWWfsw/package", we chose to split the main program and 3rd-party modules into separate directories. The main program is installed under "/opt/TWWfsw/package" and the 3rd-party modules under "/opt/TWWfsw/packagep". Because of this distinction, changes have been made to each package to search for 3rd-party modules in the auxiliary directory. This change has been made either at the source code level and compiled into the program or through the wrapper script installed to invoke the program.
/opt/TWWfsw/packager Due to the size of some packages, if they have certain runtime libraries that other packages might depend on, we split out the runtime libraries and create a separate directory containing only the libraries. This allows us to create dependencies on the smaller package, thus reducing the size of installation required to execute the program. This is currently done for CUPS, GCC, and Ghostscript.

 
Resources
Release Notes
Getting Started
Package Utilities Suite
Package Internals
Mirroring Repository
GPG Public Key
 
Package Internals
Installation directories
Package names
Startup scripts
GCC runtime directory
Perl, Python module search path