InstallationSystemWiki/InstallationSystemCVS

"Software" Documentation - Installationsystem - CVS usage

The installation system is designed to work CVS to delevelop and maintain components. It can be instructed to checkout components from a CVS repository and keep them in sync with it. This page describes how the installation system can be used together with the CVS repositories at the CeBiTec.

Table of Contents

• Requirements
• Getting the installation system
• Getting components
• Keeping components in sync
• Updating component configuration
• Differences to production use
• Example: Checking out GenDB

Author: Burkhard Linke

Requirements

• access to the CeBiTec network, e.g. unix account
• membership in the "gendb" unix group at CeBiTec
• CVS configured to access the repositories at the CeBiTec
• a recent version of Perl (e.g. latest 5.8. build)
• a recent version of CVS (1.11 or newer)
• XML::DOM

The lists do not includes the requirements for the components itself ! Setting up CVS correctly may require you to set the environment variables CVSROOT and CVS_RSH. Consult the CVS documentation or send a mail to the support desk.

Getting the installation system

The installation system itself is maintained in a CVS repository at the CeBiTec site. After verifying that your CVS access works check out the bioinfo/bridge_install repository from the CeBiTec CVS. This will only check out the CVS version of the installation system. Use the install.sh script to create a base installation system:

sh install.sh <some directory>

The directory will be created if not already existing and the script files that are part of the installation system will be adopted to its path.

Notes:

• It's recommended not to check out CVS stuff in your home directory. Use a subdirectory instead.
• The installation system is work in progress, so you may want to check for updates from time to time.
• You can use the install script to overwrite an existing installation system; components and their configuration will not be affected
• You CANNOT move the content of the installation directory to some other place. Some pathes are hardcoded in a number of perl scripts by the install.sh script.