InstallationSystemWiki/InstallationSystemLayout: Difference between revisions

From BRF-Software
Jump to navigation Jump to search
No edit summary
 
imported>BurkhardLinke
No edit summary
(No difference)

Revision as of 11:15, 1 December 2004

"Software" Documentation - Installationsystem - Layout

The installation system creates a directory structure containing scripts, perl module, compoment directories and so on. This page describes the structure and the meaning of the directories and their content.

/bin sub directory containing the scripts to manage and installation or that are part of an installed component
install_module installs a new component from a tarball
list_module lists all installed components
activate_module activates a component (makes it available in the environment
remove_module removes a component
validate_module lists files that have been changed after installation
add_cvs_repository installs a new component from a CVS server
component_start wrapper scripts to start perl scripts provided by a component
symlinks shortcuts to start perl scripts of some component
/share perl modules and management files of the installation system, sub directories for compoments
config scripts to create the runtime environment, e.g. setting up pathes and environment variables
exec templates for the component start scripts
modules.dtd, modules.xml component management and configuration
perl perl modules of the installation system
component-version subdirectory containing a component. The layout of the directories depends on the component
component symlink to the activated version of a component. These links are used within various environment variables to point to the right version of a component
/var storage for data that is generated by the components. Each components uses a sub directory to keep the data seperated
/tmp used during module installation for extracting tarballs or as CVS working directory. Content may be removed after the installation has finished

Note:

  • The components currently available to not include architecture dependent files.

Author: Burkhard Linke