Configuration files - CVS and misc

CVS itself was installed onto the shared network drive S:\

The remainder of this section covers some of the technicalities of the CVS installation and references the CVS documentation. The CVS installation is covered in more simple terms in the sections Taking control, Releasing a form, etc etc.

Before controlling the Uniface source code in CMTOOL format the following directory tree existed.

p:\Nettest

\Sources

\applications

\components

\globals

\glyphs

\menus

\other

\registers

\subsystems

\sub-types

\tables

\templates

\type-libraries

The ‘Sources’ directory was renamed ‘s’ for the cvs import operation.

p:\Nettest

\s

\applications

\components

\globals

\glyphs

\menus

\other

\registers

\subsystems

\sub-types

\tables

\templates

\type-libraries

The cvs operations were performed from the p:\nettest\s directory. The cvs import operation effectively re-created the p:\nettest\sources directory tree under configuration control. Please read the CVS README topic, which describes this CVS installation process.

The final result was:

p:\Nettest

\s

\applications

\components

\globals

\glyphs

\menus

\other

\registers

\subsystems

\sub-types

\tables

\templates

\type-libraries

\Sources

\applications

\components

\globals

\glyphs

\menus

\other

\registers

\subsystems

\sub-types

\tables

\templates

\type-libraries

\Cvsroot

Then the ‘additional’ directory tree ‘p:\nettest\s’ was removed.

Configuration Files

Joins File
ASN file
CVS and misc

How to use the driver with a configuration management solution (cont.)

Configuration information
Taking control
Releasing a form
Checking a form in
Releasing a form and application model
Releasing registers
Adding a form
Differences
Merging code changes
Final notes

UD6 Overview
A methodology to Uniface source code control

Further Information

CVS README
CVS Help
Other Links

$Revision: 1.11 $ $Date: 2011/02/28 02:56:33 $[go to top]