[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
C.1 The modules file
The ‘modules’ file records your definitions of
names for collections of source code. CVS will
use these definitions if you use CVS to update the
modules file (use normal commands like add
,
commit
, etc).
The ‘modules’ file may contain blank lines and comments (lines beginning with ‘#’) as well as module definitions. Long lines can be continued on the next line by specifying a backslash (‘\’) as the last character on the line.
There are three basic types of modules: alias modules, regular modules, and ampersand modules. The difference between them is the way that they map files in the repository to files in the working directory. In all of the following examples, the top-level repository contains a directory called ‘first-dir’, which contains two files, ‘file1’ and ‘file2’, and a directory ‘sdir’. ‘first-dir/sdir’ contains a file ‘sfile’.
C.1.1 Alias modules | The simplest kind of module | |
C.1.2 Regular modules | ||
C.1.3 Ampersand modules | ||
C.1.4 Excluding directories | Excluding directories from a module | |
C.1.5 Module options | Regular and ampersand modules can take options | |
C.1.6 How the modules file “program options” programs are run | How the modules “program options” programs are run. |