Perforce Repository Setup Dialog

Help index

Introduction

This source code manager was provided by a customer and is not maintained by eXept itself. It provides access to a perforce (P4) repository.

For a general introduction to source code management, please consult the "Programmer's Guide to ST/X - Sourcecode & Revision Management".

P4 Settings Dialog

P4 Binary Executable Path

Optionally specifies the path to the "p4" command.
A full path is only required if you do not have cvs installed along the default PATH, or if you want to use your own private version of the p4 command. Usually, the default "p4" is ok for the system to find the perforce command.

Perforce Root Default

Specifies the perforce ROOT for all classes which do not belong to a module listed in the per-module list.
I.e. its the fallback P4Root used for all other classes, not listed below.

Per Module Setup

In ST/X, class packages form a hierarchical tree and their files are mapped in the source repository to subdirectories below a so called module root. The module itslef is specified by the first component of a package path. For example:
The "Array"-class is found in the "stx:libbasic" package.
Therefore, its module is "stx" and its container is found in the "libbasic" sub-directory, of the repository which has been associated to the "stx" module.

Placing your own packages into a separate module (typically, you would use your company name as module-name) and specifying a separate root for this module, allows you to manage your own classes in a separate source code repository.
Of course, this also allows for multiple independent repositories to be defined and maintained in bigger organizations.

Source Cache

Performing a slow checkOut operation for every class which is visited in the browser does slow down the system's responses - especially the search functions (senders/string-search etc.) may become unusably slow.
To avoid this, the sourcecode-manager keeps track of already checked-out classes and remembers those in a cacheDirectory. This cache may grow over time, as it remembers multiple versions of all classes of which source code has ever been asked for.
The default location for this cache is "/tmp/stx_sourceCache" (unix) or "<userDefault>\local files\Temp\stx_sourceCache" (windows).
Over time, this directory may grow and should be purged from time to time (The purge operation removes old versions in the cache and leaves the youngest only).
It is not dangerous, to remove those old files, as they will be re-checked out as required (for example, when you do a "compare with previous" operation later).


Copyright © eXept Software AG, all rights reserved


Doc $Revision: 1.2 $ $Date: 2012/03/16 11:08:27 $