Chapter 10. Manual Installation

Table of Contents
10.1. D-I-Y Installation for the Impatient
10.2. D-I-Y Installation of the Executable Programs
10.3. Installation and Configuration of the Source Code Repository
10.4. Installation of the Package Pools
10.5. Setup of a global configuration file
10.6. Other Configuration Files: PkgBase.DefaultData and pkgconf.cbcl
10.7. Setup of the ComPact Resource Service

This chapter contains a description of all steps necessary to install Elego ComPact on one or more computers of a network. Some of these steps are also performed by the graphical installer of Elego ComPact (copying of programs, demo data, and documentation). In most cases is will be necessary to perform some additional steps manually, like setting up shared package pools and setting permissions for the repository and pools. Those who prefer the graphical installer will also find some background information about all posibilities for setting up remote repository access.

10.1. D-I-Y Installation for the Impatient

If you are impatient or just want to get an impression of the various programs of Elego ComPact, you can try to follow the steps enumerated below. If anything fails or does not work as expected, you will have to fall back to reading the documentation.

  1. Copy the executable programs from /compact/your operating system on the CD into a directory that is in your path, e.g. /usr/local/bin. The graphical installer creates a directory structure below a compact root directory looking like this:

        compact / bin       -- executable ComPact programs
                / config    -- configuration resources
                / doc       -- manuals
                / exkit     -- example data for tutorials and tests
                / pools     -- global standard package caches
    
    This structure is usually located at /usr/local or /opt. Its root directory is called COMPACTROOT in the configuration resources and this text. In order to remain compatible with the standard installation, we recommend using the same structure. You may of course add symbolic links for the programs as needed or include the bin directory of this structure in the standard program search path.

  2. Copy the example repository from the CD (/demo/cvs) to your disk.

  3. Create directories for your local, project, and global package pools, e.g. {HOME}/pools/{local,project,global}. This simple approach will of course not work for sharing pools.

  4. Copy the central configuration file from /config/compactrc to {COMPACTROOT}/config/compactrc and / or {HOME}/.compactrc for your personal use.

  5. Customize at least the following values of this configuration file: poolprefix, localpool, projectpool, globalpool, configuration, bindir, repository, editor, httpd-port, browser.

  6. You are now ready to run any Elego ComPact program. Try the following commands:

    1. pkgm -collection gnu -checkout head prj

    2. cd gnu/prj/gnu-cvs

    3. Set the environment variable PRJ_ROOT to the directory in which you issued the first checkout command. The syntax for this depends on your shell, use set, setenv, export commands as needed. Alternatively, edit PrjDesc and change the collection root to the directory where you checked out the gnu collection.

    4. prjm -checkout head

    5. prjm -check

    6. prjm -nodep -buildlocal



    You have now checked out the project description of the gnu-cvs project, checked out all packages belonging to the project, checked the correctness and consistency of the project, and finally built the project using your local package pool. You may of course do all these things using the graphical user interface of Elego ComPact. Start it by simply typing ComPactHTTPd, and you're on your way.