Index: CMT/v1r19/doc/CMTDoc.html
===================================================================
--- CMT/v1r19/doc/CMTDoc.html	(revision 18)
+++ CMT/v1r19/doc/CMTDoc.html	(revision 21)
@@ -23,5 +23,5 @@
 <center>Christian Arnault</center>
 <center><tt>arnault@lal.in2p3.fr</tt></center></h2>
-<center><i>Document revision date : 2005-03-21</i></center><hr><h2><a href="#index">General index</a></h2>
+<center><i>Document revision date : 2005-03-30</i></center><hr><h2><a href="#index">General index</a></h2>
 <hr><h2><a name="Presentation"></a><a href="#index"><tt>&nbsp;1</tt></a> - Presentation</h2>
 <blockquote>
@@ -270,10 +270,11 @@
       <i>sub-projects</i>
        which correspond to the practical
-            organization of the software developments.</p>
-      <p>There are no constraints on the number of such areas into
-              which <tt>CMT</tt>
-       packages are installed. We'll see <a HREF="#Localizing a package">later</a>
-       how the different areas
-              or sub-projects can be declared and identified by
+            organization of the software base.</p>
+      <p>There are no constraints on the number of such sub-projects
+              or areas into which <tt>CMT</tt>
+       packages are installed. We'll
+              see <a HREF="#Localizing a package">later</a>
+       how the
+              different sub-projects can be declared and identified by
       <tt>CMT</tt>
     .</p>
@@ -400,5 +401,5 @@
     <li>a structuration in software domains, such as Reconstruction,
         Simulation, Graphics, Core, etc.</li>
-    <li>how responsibilities or management policy are defined and
+    <li>how responsibilities or management policies are defined and
         assigned </li>
     <li>reusing or sharing different software products from
@@ -406,41 +407,215 @@
 </ul>
   <p>Considering the simple structuring aspects of sub-projects, two
-      important configuration parameters handled by CMT must be
-      understood before attempting to manage packages. These are the
-    following environment variables:</p>
+      important configuration parameters (environment variables) handled
+      by CMT must be understood before attempting to manage
+    packages:</p>
   <ul>
-    <li><tt>CMTPROJECTPATH</tt>
-  </li>
-    <li><tt>CMTPATH</tt>
-  </li>
+      <li><a href="#CMTPROJECTPATH"><tt>CMTPROJECTPATH</tt>
+    </a>
+     for a
+          global specification of where projects can be found. This
+          specification should be considered as the standard mechanism for
+          structuring the software base since from it, CMT can and will
+          deduce all other localization parameters (like
+    <tt>CMTPATH</tt>
+    ).<p></p>
+  </li>
+      <li><a href="#CMTPATH"><tt>CMTPATH</tt>
+    </a>
+     offers a more
+          internal mechanism for localizing packages. It's not generally
+          meant to be defined manually since CMT will construct it from
+    <tt>CMTPROJECTPATH</tt>
+    . However, it's important to understand
+          how this configuration parameter is used to locate
+        packages.</li>
 </ul>
-<hr><h3><a name="CMTPROJECTPATH"></a><a href="#index"><tt>&nbsp;4.&nbsp;1</tt></a> - CMTPROJECTPATH</h3>
+  <p>Projects receive detailed descriptions or specifications in a
+      dedicated <i>project file</i>
+  , always located in a <tt>cmt</tt>
+      directory at their top directory level, and named
+  <tt>cmt/project.cmt</tt>
+  . It can receive the following
+    specifications:</p>
+<pre class="cmt">
+project &lt;project-name&gt;          [1]
+<i>project-use specifications...</i>   [2]
+<i>strategy specifications...</i>      [3]
+</pre>
+  <ol>
+    <li>The project name specified here takes precedence over the
+          project name specified in the directory structure. However when
+    <tt>CMTPROJECTPATH</tt>
+     is not specified, this may cause
+          conflicts in the localization of projects. In this case it's
+          highly recommended to always use the same naming convention in
+          project files as in the directory hierarchy.<p></p>
+  </li>
+    <li>Projects are hierarchized as a directed acyclic graph. The
+          minimal hierarchy simply corresponds to the order of the
+    <tt>CMTPATH</tt>
+     items. A more complex hierarchy can be
+          specified through use statements between sub-projects. This
+          hierarchy also defines a <i>parent/child</i>
+     relationship between
+          projects. If a project <tt>A</tt>
+     uses another project
+    <tt>B</tt>
+    , <tt>A</tt>
+     is also named the <i>parent</i>
+     and
+    <tt>B</tt>
+     the <i>child</i>
+    <p></p>
+  </li>
+    <li>CMT Strategies (for build or setup) are separately
+           collected into each project. Therefore one can apply different
+           strategies to different sub-projects. The strategy
+           specifications may appear in requirements file of any package
+    of a project or in the <tt>cmt/project.cmt</tt>
+     project file.
+      <p>By default a project inherits the strategies of its
+             parents. Or if it's the top project, it follows the default
+             strategies defined by CMT (Refer to this 
+      <a href="#The default strategies defined in CMT">appendix</a>
+           to see the default strategies currently defined by CMT).</p>
+    <p></p>
+  </li>
+</ol>
+<hr><h3><a name="The project file"></a><a href="#index"><tt>&nbsp;4.&nbsp;1</tt></a> - The project file</h3>
+<blockquote>
+<p>The project file can be created using the command:</p>
+<pre>
+&gt; cmt create_project &lt;project-name&gt; [&lt;release&gt;] [&lt;path&gt;]</pre>
+  <p>This will create the complete directory hierarchy from the
+        current directory (or, when it is specified from the optional
+        project path). It will also create a project file containing the
+      project name.</p>
+    <blockquote><i>Note that the &lt;release&gt; argument may be
+          left empty (or to an empty string). In this case, the directory
+          hierarchy will be limited to one level devoted to the project
+        name.</i>
+</blockquote>
+<pre>
+&lt;path&gt;/&lt;project-name&gt;/&lt;release&gt;/cmt/project.cmt
+&lt;path&gt;/&lt;project-name&gt;/cmt/project.cmt</pre>
+<p>As an example, we create the following projects:</p>
+<pre>
+&gt; cmt create_project WorkArea "" /test
+&gt; cmt create_project ProjectA 1.0 /test
+&gt; cmt create_project ProjectB 1.0 /test</pre>
+  <p>And we fill <tt>CMTPATH</tt>
+ with:</p>
+<pre>
+/test/WorkArea:/test/ProjectA/1.0:/test/ProjectB/1.0</pre>
+  <p>Then the following projects will appear displayed from bottom
+      to top as</p>
+<pre>
+&gt; cd /test/WorkArea
+&gt; cmt show projects 
+<i><font COLOR="#000077" face="courier new, courier">WorkArea (in /test/WorkArea) (current)
+  ProjectA 1.0 (in /test/ProjectA/1.0)
+    ProjectB 1.0 (in /test/ProjectB/1.0)</font></i></pre>
+  <p>Of course the preferred way to characterize this software
+        base should rather be based on specifying the relationships
+        between those three sub-projects, through the use statements in
+      the projects files.</p>
+  <p>For instance in our little example, we could add the
+      following statement into the project file of WorkArea:</p>
+<pre>
+use ProjectA 1.0</pre>
+<p>and the following statement into the project file of ProjectB:</p>
+<pre>
+use ProjectB 1.0</pre>
+  <p>Then instead of specifying <tt>CMTPATH</tt>
+   we'd rather
+        simply define <tt>CMTPROJECTPATH</tt>
+ as:</p>
+<pre>
+/test</pre>
+</blockquote>
+<hr><h3><a name="Projects and strategies"></a><a href="#index"><tt>&nbsp;4.&nbsp;2</tt></a> - Projects and strategies</h3>
+<blockquote>
+  <p>Every strategy setting defines two mutually exclusive tags
+      and activates one of them.</p>
+<pre class="cmt">
+&lt;project&gt;_&lt;have_item&gt; 
+&lt;project&gt;_&lt;have_not_item&gt; </pre>
+<p>Examples</p>
+<pre class="cmt">
+&lt;project&gt;_prototypes
+&lt;project&gt;_no_prototypes
+&lt;project&gt;_with_install_area
+&lt;project&gt;_without_install_area
+&lt;project&gt;_config
+&lt;project&gt;_no_config
+&lt;project&gt;_root
+&lt;project&gt;_no_root
+&lt;project&gt;_cleanup
+&lt;project&gt;_no_cleanup</pre>
+  <p>In particular, the installation area mechanism is strongly
+        connected with the project hierarchy. This happens through
+      several mechanisms:</p>
+  <ul>
+    <li>The <tt>&lt;project&gt;</tt>
+     parameter is expanded in the
+    <tt>cmtpath_pattern</tt>
+     construct in addition to the
+    <tt>&lt;path&gt;</tt>
+     parameter. This parameter is assigned
+            the name of the project associated with the running
+    <tt>CMTPATH</tt>
+     entry.  <p></p>
+  </li>
+    <li>The <tt>&lt;project&gt;</tt>
+     parameter is also available
+            for normal patterns. In this case it is assigned the project
+            name associated with the cmtpath parameter for the current
+            package.<p></p>
+  </li>
+    <li>Every project defines a tag of the same name, and the tag
+            of the current project is active.<p></p>
+  </li>
+    <li>The <tt>cmt_installarea_prefix</tt>
+     macro is specialized
+    <i>per project</i>
+     and every project may override the
+    <tt>&lt;project&gt;_installarea_prefix</tt>
+     macro. The default
+            value of any <tt>&lt;project&gt;_installarea_prefix</tt>
+     is
+    <tt>${cmt_installarea_prefix}</tt>
+    <p></p>
+  </li>
+</ul>
+</blockquote>
+<hr><h3><a name="CMTPROJECTPATH"></a><a href="#index"><tt>&nbsp;4.&nbsp;3</tt></a> - CMTPROJECTPATH</h3>
 <blockquote>
   <p>This is an environment variable containing a search list,
-        very similar to the well know <tt>PATH</tt>
-   environment
-        variable, containing a list of file paths where CMT projects can
-        be found. The syntax of this search list follows the standard
-        syntax of search lists, i.e. items are separated using a
-  <tt>:</tt>
+        very similar to the well know Unix or Windows <tt>PATH</tt>
+        environment variable, containing a list of file paths where CMT
+        projects can be found. The syntax of this search list follows
+        the standard syntax of search lists, i.e. items are separated
+        using a <tt>:</tt>
    character on Unix and a <tt>;</tt>
-   character on
-      Windows.</p>
-      <p><blockquote><i>One should understand this search list as the primary
-            mechanism to locate sub-projects in the software base, and
-            therefore packages. This in particular can completely replace
-            the <tt>CMTPATH</tt>
-      -based search mechanism for packages that
-            was used before <tt>v1r18</tt>
-      . However the two mechanisms are
-          still supported together.</i>
+   character
+      on Windows.</p>
+      <p><blockquote><i>One should understand this search list as the
+            primary mechanism to locate sub-projects in the software base,
+            and therefore packages. This in particular can completely
+            replace the <tt>CMTPATH</tt>
+      -based search mechanism for packages
+            that was used before <tt>v1r18</tt>
+      . However the two mechanisms
+            are still both supported and in fact interact with each
+          other.</i>
   </blockquote>
 </p>
-  <p>A sub-project in itself is a two-level directory structure,
+  <p>A sub-project in itself is a multi-level directory structure,
         located below one of the items of this search list, and composed
       of:</p>
   <ul>
   <li>the sub-project name</li>
-  <li>the sub-project release</li>
+  <li>the sub-project release (which may span several directory levels)</li>
 </ul>
 <p>Then, below this directory structure, we find</p>
@@ -508,5 +683,5 @@
   </li>
 </ul>
-  <p>This search list is considered to interpret the <i>use</i>
+  <p>This search list is used to interpret the <i>use</i>
         statements written in the project files. This project use
       statement takes the form:</p>
@@ -541,17 +716,21 @@
 use Core 1.0
 use ProductA 1.1.2</pre>
-    <p><i>Note that sub-project release identifiers are considered
-        using a perfect-match principle.</i>
+    <p><i>Note that sub-project release identifiers are always
+        considered using a perfect-match principle.</i>
 </p>
   <p>Structuring the set of sub-projects comprising a software
-        base is sufficient to permit CMT to find all sub-projects and
-        thus all packages in them. Defining <tt>CMTPROJECTPATH</tt>
+        base is sufficient to permit CMT to find <i>all</i>
+   sub-projects
+        and thus <i>all</i>
+   packages in them. Defining
+  <tt>CMTPROJECTPATH</tt>
   <i>and</i>
-   installing the list of use statements in all
-        appropriate project files entirely suppress the need of manually
-        defining the <tt>CMTPATH</tt>
- search list.</p>
-</blockquote>
-<hr><h3><a name="CMTPATH"></a><a href="#index"><tt>&nbsp;4.&nbsp;2</tt></a> - CMTPATH</h3>
+   installing the list of use
+        statements in all appropriate project files entirely suppress
+        the need of manually defining the <tt>CMTPATH</tt>
+   search
+      list.</p>
+</blockquote>
+<hr><h3><a name="CMTPATH"></a><a href="#index"><tt>&nbsp;4.&nbsp;4</tt></a> - CMTPATH</h3>
 <blockquote>
   <p>This is an environment variable containing a search list,
@@ -566,13 +745,65 @@
       Windows.</p>
       <p><blockquote><i>When the software base is organized and
-            configured using the <tt>CMTPROJECTPATH</tt>
-       search list and
-            project-use statements in the project files, this search list is
-            automatically and internally generated by CMT, and therefore it
-            should not be manually defined nor manipulated. If this is your
-          case, you can skip this section</i>
+              configured using the <a href="#CMTPROJECTPATH"><tt>CMTPROJECTPATH</tt>
+      </a>
+       search list
+            and project-use statements in the project files, this search
+            list is automatically and internally generated by CMT, and
+            therefore it should not be manually defined nor manipulated. If
+            this is your case, you can skip this
+          section</i>
   </blockquote>
 </p>
-<p>There should be one entry</p>
+  <p>It is possible to manually define this search list (when
+  <tt>CMTPROJECTPATH</tt>
+   is not defined or when project files are
+      not provided)</p>
+  <p>There should be one entry per package area, and the list is
+        ordered. The order of items is used to prioritize the package
+      search.</p>
+  <p><tt>CMTPATH</tt>
+ can be specified:</p>
+  <ul>
+    <li>as the environment variable named <tt>CMTPATH</tt>
+<pre>
+sh&gt; export CMTPATH=/home/arnault/mydev:/ProjectB </pre>
+<pre>
+bat&gt; set CMTPATH=/home/arnault/mydev;/ProjectB </pre>
+              or (in a <tt>requirements</tt>
+     file) 
+<pre class="cmt">
+path_append CMTPATH "/home/arnault/mydev"
+path_append CMTPATH "/ProjectB"</pre>
+  </li>
+    <li>in <tt>.cmtrc</tt>
+     files, which can be located either in
+            the current directory, in the <i>home</i>
+     directory of the
+            developper or in <tt>${CMTROOT}/mgr</tt>
+    . The syntax to use in this
+            configuration file is:
+<pre>
+CMTPATH=/home/arnault/mydev:/ProjectB </pre>
+  </li>
+    <li>In the Windows environment, this configuration parameter
+            may also be installed as a <i>Registry</i>
+     under the alternate
+            keys:
+      <ul>
+        <li><tt>HKEY_LOCAL_MACHINE/Software/CMT/path</tt>
+      </li>
+        <li><tt>HKEY_CURRENT_USER/Software/CMT/path</tt>
+      </li>
+    </ul>
+  </li>
+</ul>
+    <blockquote><i>The project file (i.e. the file
+    <tt>cmt/project.cmt</tt>
+    ), when it exists for the current
+          package (i.e. upstream in the directory hierarchy), also
+          provides an automatic value for the <tt>CMTPATH</tt>
+     search
+        list.</i>
+</blockquote>
 </blockquote>
 </blockquote>
@@ -645,9 +876,10 @@
 Installing the cmt directory
 Creating a new project file </font></i></pre>
-  <p>This creates a project structure (i.e. a
-  <tt>cmt/project.cmt</tt>
-   file) from the current directory. Once
+  <p>This creates a project structure
+  <tt>Dev/cmt/project.cmt</tt>
+   from the current directory. Once
       this project has been created we have a complete environment to
-    start creating packages and working out our software base.</p>
+      start creating packages below <tt>Dev</tt>
+ and working out our software base.</p>
   <p> A package is primarily defined by a <i>name</i>
    and a
@@ -660,10 +892,10 @@
 </p>
 <pre>
-csh&gt; cd mydev
+csh&gt; cd Dev
 csh&gt; cmt create Foo v1
 <i><font COLOR="#000077" face="courier new, courier">------------------------------------------
 Configuring environment for package Foo version v1.
 CMT version v1r18p20041201.                              [1]
-Root set to /home/arnault/mydev.
+Root set to /home/arnault/Dev.
 System is Linux-i686                                     [2]
 ------------------------------------------
@@ -865,15 +1097,16 @@
   <p>The first ingredient we need at this level is to understand how
       projects themselves are localized, since packages will be found
-    inside project areas.</p>
-  <p>Projects are localized according to the <tt>CMTPATH</tt>
-   path
-      list. Thus it is <i>always</i>
-   required to define this environment
-      variable as soon as several project areas are expected. However,
-      there is one special case where this path list can be avoided,
-      i.e. when only one project area is considered. In this case, the
-      knowledge of this single project area can simply be deduced from
-      the detection of the project file, created at the top of its disk
-    space.</p>
+      inside project areas. You should therefore refer to the 
+  <a href="#Defining and managing projects">section on projects</a>
+        where the complete mechanism based on <a href="#CMTPROJECTPATH"><tt>CMTPROJECTPATH</tt>
+  </a>
+     or <a href="#CMTPATH"><tt>CMTPATH</tt>
+  </a>
+ is described.</p>
+  <p>However, there is one special case where this path list can be
+      avoided, i.e. when only one project is considered. In this case,
+      the knowledge of this single project area can simply be deduced
+      from the detection of the project file, created at the top of its
+    disk space.</p>
   <p>A given version of a given package is always referred to by
       using a <i>use</i>
@@ -906,40 +1139,12 @@
      is
         absolute (case #3), </li>
-    <li> the access paths optionally registered in the configuration
-          parameter - see below - <tt>CMTPATH</tt>
+    <li> the access paths registered in the configuration parameter
+      <a href="#CMTPATH"><tt>CMTPATH</tt>
+    </a>
      (and in decreasing
         priority, the first element being searched for first).</li>
 </ol>
-<blockquote><hr>
-  <i>
-          The configuration parameter <tt>CMTPATH</tt>
-   can be specified
-          either in the environment variable named <tt>CMTPATH</tt>
-   or in
-  <tt>.cmtrc</tt>
-   files, which can themselves be located either in
-          the current directory, in the <i>home</i>
-   directory of the
-          developper or in <tt>${CMTROOT}/mgr</tt>
-  . In the Windows
-          environment, this configuration parameter may also be
-          installed as a <i>Registry</i>
-   under either the keys:
-    <ul>
-      <li><tt>HKEY_LOCAL_MACHINE/Software/CMT/path</tt>
-    </li>
-      <li><tt>HKEY_CURRENT_USER/Software/CMT/path</tt>
-    </li>
-  </ul>
-    <p>The project file (i.e. the file <tt>cmt/project.cmt</tt>
-    ),
-            when it exists for the current package area, is able to
-            provide an automatic value for the <tt>CMTPATH</tt>
-     search
-          list.</p>
-</i>
-<hr></blockquote>
   <p>If the <i>path</i>
-  argument is specified as a relative path
+   argument is specified as a relative path
       (case #2 above) (ie. there is no leading <i>slash</i>
    character or
@@ -950,36 +1155,10 @@
       from the list specified in the <tt>CMTPATH</tt>
    configuration
-      parameter, then using the default root; and the offset is appended
-    at each searched location.</p>
-  <p>The <tt>CMTPATH</tt>
-   parameter is thus used as a search list for
-      the packages, and the individual paths are separated in this list
-      by <i>colons</i>
-   (<i>semi-colons</i>
- on Windows). </p>
-  <p>A very typical usage of thie <tt>CMTPATH</tt>
-   search list is to
-      assign one entry per project or sub-project considered in the
-      workning context. This is consistent with an approach where every
-      sub-project will have a dedicated management style, access rights,
-    rsponsible persons, etc.</p>
-  <p>As an example, if we specify the <tt>CMTPATH</tt>
-   parameter as
-    follows : </p>
+      parameter; and the offset is appended at each searched
+    location.</p>
+  <p>As an example, if the <tt>CMTPATH</tt>
+ parameter contains: </p>
 <pre>
-csh&gt; setenv CMTPATH /home/arnault/mydev:/ProjectB </pre>
-<pre>
-sh&gt; export CMTPATH=/home/arnault/mydev:/ProjectB </pre>
-<pre>
-bat&gt; set CMTPATH=/home/arnault/mydev;/ProjectB </pre>
-    or (in a <tt>requirements</tt>
- file) 
-<pre class="cmt">
-path_append CMTPATH "/home/arnault/mydev"
-path_append CMTPATH "/ProjectB"</pre>
-    or (in a <tt>.cmtrc</tt>
- file) 
-<pre>
-CMTPATH=/home/arnault/mydev:/ProjectB </pre>
+/home/arnault/mydev:/ProjectB </pre>
   <p>Then a <i>use</i>
    statement (defined within a given package)
@@ -1031,167 +1210,10 @@
 </p>
 </blockquote>
-<hr><h2><a name="The concept of project"></a><a href="#index"><tt>&nbsp;7</tt></a> - The concept of project</h2>
-<blockquote>
-    The purpose of the concept of <i>project</i>
- or <i>sub-project</i>
-    is to structure the software bases developed using CMT. This
-    concept basically assigns a semantics to the physical structuring
-    mechanism of the software areas already described by the <tt>CMTPATH</tt>
-    search list.
-  <p>Some general properties can describe the knowledge of projects
-    in CMT:</p>
-  <ul>
-    <li>One project is always explicitly or implicitly associated
-          with every CMTPATH entry.<p></p>
-  </li>
-    <li>Every project can be <i>named</i>
-     inside a dedicated text
-          file (the <i>project file</i>
-    ) named <tt>cmt/project.cmt</tt>
-    ,
-          located immediately below the corresponding <tt>CMTPATH</tt>
-          entry. The format of this file is
-<pre class="cmt">
-project &lt;project-name&gt;
-<i>strategy specifications...</i></pre>
-    <p></p>
-  </li>
-    <li>When not explicitly named, a sub-project is automatically
-          assigned the default name <tt>Project&lt;N&gt;</tt>
-     by CMT,
-          where <tt>&lt;N&gt;</tt>
-     is the sequence number of the project
-          in the list<p></p>
-  </li>
-    <li>The project file can be created using one of the commands: 
-<pre>
-  &gt; cmt create_project &lt;project-name&gt;
-  &gt; cmt -project=&lt;project-name&gt; create ...
-  &gt; cmt -project=&lt;project-name&gt; checkout ...</pre>
-    <p></p>
-  </li>
-    <li>When being within one project area where a project file has
-          been installed, its CMTPATH is automatically generated as the
-          location where the first visible project file is
-          detected.<p></p>
-  </li>
-    <li>The same project may be associated with several CMTPATH
-           entries, typically when one entry is a development area of
-           another one being the production area of the same
-           sub-project<p></p>
-  </li>
-    <li>Since CMTPATH entries are ordered the projects are
-           hierarchized accordingly. The last CMTPATH entry (i.e. the
-           rightmost one) corresponds to the top project while the first
-           CMTPATH entry (i.e. the leftmost one) corresponds to the bottom
-           project. A project may have a predecessor and/or a successor.
-      <p>As an example, suppose we have set up the following
-      <tt>CMTPATH</tt>
-    :</p>
-<pre>
-$HOME/work-for-A:/ProjectA:/ProjectB</pre>
-             Then the following projects will appear displayed from bottom
-             to top as
-<pre>
-&gt; cmt show projects 
-<i><font COLOR="#000077" face="courier new, courier">Project1 (in /.../work-for-A)
-Project2 (in /ProjectA)
-Project3 (in /ProjectB)
-CMT (in /afs/cern.ch/sw/contrib)</font></i></pre>
-             And if projects have been explicitly named this display will become:
-<pre>
-&gt; cmt show projects 
-<i><font COLOR="#000077" face="courier new, courier">A (in /.../work-for-A)
-A (in /ProjectA)
-Project3 (in /ProjectB)
-CMT (in /afs/cern.ch/sw/contrib)</font></i></pre>
-    <p></p>
-  </li>
-    <li>CMT Strategies (for build or setup) are separately
-           collected into each project. Therefore one can apply different
-           strategies to different sub-projects. The strategy
-           specifications may appear in requirements file of any package
-           of a project or in the <tt>cmt/project.cmt</tt>
-     project file.
-      <p>By default a project inherits the strategies of its
-             predecessor. Or if it's the top project, it follows the default
-             strategies defined by CMT (Refer to this 
-      <a href="#The default strategies defined in CMT">appendix</a>
-       to see the default
-           strategies currently defined by CMT).</p>
-    <p></p>
-  </li>
-    <li>A CMT command displays the projects and their associated CMTPATH: 
-<pre>
-&gt; cmt show projects
-&gt; cmt show project &lt;project-name&gt;</pre>
-    <p></p>
-  </li>
-    <li>The installation area mechanism is strongly connected with
-           the <tt>CMTPATH</tt>
-     hierarchy. Therefore it will also be connected with
-           the project concept. This will happen through several
-           mechanisms:<p></p>
-      <ul>
-        <li>The <tt>&lt;project&gt;</tt>
-         parameter is expanded in the
-        <tt>cmtpath_pattern</tt>
-         construct in addition to the
-        <tt>&lt;path&gt;</tt>
-         parameter. This parameter is assigned
-                   the name of the project associated with the running
-        <tt>CMTPATH</tt>
-         entry.  <p></p>
-      </li>
-        <li>The <tt>&lt;project&gt;</tt>
-         parameter is also available
-                   for normal patterns. In this case it is assigned the
-                   project name associated with the cmtpath parameter for the
-                   current package.<p></p>
-      </li>
-        <li>Every project defines a tag of the same name, and the
-                   tag of the current project is active.<p></p>
-      </li>
-        <li>The <tt>cmt_installarea_prefix</tt>
-         macro is specialized
-        <i>per project</i>
-         and every project may override the
-        <tt>&lt;project&gt;_installarea_prefix</tt>
-         macro. The
-                   default value of any
-        <tt>&lt;project&gt;_installarea_prefix</tt>
-         is
-        <tt>${cmt_installarea_prefix}</tt>
-        <p></p>
-      </li>
-    </ul>
-    <p></p>
-  </li>
-    <li>Every strategy setting defines two mutually exclusive tags and activates one of them.
-<pre class="cmt">
-&lt;project&gt;_&lt;have_item&gt; 
-&lt;project&gt;_&lt;have_not_item&gt; </pre>
-             Examples 
-<pre class="cmt">
-&lt;project&gt;_prototypes
-&lt;project&gt;_no_prototypes
-&lt;project&gt;_with_install_area
-&lt;project&gt;_without_install_area
-&lt;project&gt;_config
-&lt;project&gt;_no_config
-&lt;project&gt;_root
-&lt;project&gt;_no_root
-&lt;project&gt;_cleanup
-&lt;project&gt;_no_cleanup</pre>
-    <p></p>
-  </li>
-</ul>
-</blockquote>
-<hr><h2><a name="Assigning semantics to packages. Common practices"></a><a href="#index"><tt>&nbsp;8</tt></a> - Assigning semantics to packages. Common practices</h2>
+<hr><h2><a name="Assigning semantics to packages. Common practices"></a><a href="#index"><tt>&nbsp;7</tt></a> - Assigning semantics to packages. Common practices</h2>
 <blockquote>
     Generally speaking, CMT makes no assumption on how or why is used
     a package. However past experience has shown that packages can be
     categorized according to their purpose or their type of contents.
-<hr><h3><a name="The primary package"></a><a href="#index"><tt>&nbsp;8.&nbsp;1</tt></a> - The primary package</h3>
+<hr><h3><a name="The primary package"></a><a href="#index"><tt>&nbsp;7.&nbsp;1</tt></a> - The primary package</h3>
 <blockquote>
       This is the most general and basic pakage type, which provides
@@ -1221,5 +1243,5 @@
  statements.</p>
 </blockquote>
-<hr><h3><a name="The policy package"></a><a href="#index"><tt>&nbsp;8.&nbsp;2</tt></a> - The policy package</h3>
+<hr><h3><a name="The policy package"></a><a href="#index"><tt>&nbsp;7.&nbsp;2</tt></a> - The policy package</h3>
 <blockquote>
       This kind of package only provides conventions, working methods,
@@ -1264,5 +1286,5 @@
       Then the global policy package will use them
 </blockquote>
-<hr><h3><a name="The container or management package"></a><a href="#index"><tt>&nbsp;8.&nbsp;3</tt></a> - The container or management package</h3>
+<hr><h3><a name="The container or management package"></a><a href="#index"><tt>&nbsp;7.&nbsp;3</tt></a> - The container or management package</h3>
 <blockquote>
       In large projects, it's often useful to decompose the software
@@ -1290,5 +1312,5 @@
       packages of the domain.</p>
 </blockquote>
-<hr><h3><a name="The release package"></a><a href="#index"><tt>&nbsp;8.&nbsp;4</tt></a> - The release package</h3>
+<hr><h3><a name="The release package"></a><a href="#index"><tt>&nbsp;7.&nbsp;4</tt></a> - The release package</h3>
 <blockquote>
       This package is one particular example of the container concept,
@@ -1298,5 +1320,5 @@
       assigned to the project releases themselves.
 </blockquote>
-<hr><h3><a name="The glue or interface package"></a><a href="#index"><tt>&nbsp;8.&nbsp;5</tt></a> - The glue or interface package</h3>
+<hr><h3><a name="The glue or interface package"></a><a href="#index"><tt>&nbsp;7.&nbsp;5</tt></a> - The glue or interface package</h3>
 <blockquote>
       This kind of package defines an interface to an existing
@@ -1326,5 +1348,5 @@
 </blockquote>
 </blockquote>
-<hr><h2><a name="Managing site dependent features - The CMTSITE environment variable"></a><a href="#index"><tt>&nbsp;9</tt></a> - Managing site dependent features - The CMTSITE environment variable</h2>
+<hr><h2><a name="Managing site dependent features - The CMTSITE environment variable"></a><a href="#index"><tt>&nbsp;8</tt></a> - Managing site dependent features - The CMTSITE environment variable</h2>
 <blockquote>
   <p>Software bases managed by <tt>CMT</tt>
@@ -1362,5 +1384,5 @@
       LBNL  "/auto/atlas/sw/lhcxx"</pre>
 </blockquote>
-<hr><h2><a name="Configuring a package"></a><a href="#index"><tt>10</tt></a> - Configuring a package</h2>
+<hr><h2><a name="Configuring a package"></a><a href="#index"><tt>&nbsp;9</tt></a> - Configuring a package</h2>
 <blockquote>
   <p>The first ingredient of a proper package configuration is the
@@ -1461,5 +1483,5 @@
 </ul>
 </blockquote>
-<hr><h2><a name="Selecting a specific configuration"></a><a href="#index"><tt>11</tt></a> - Selecting a specific configuration</h2>
+<hr><h2><a name="Selecting a specific configuration"></a><a href="#index"><tt>10</tt></a> - Selecting a specific configuration</h2>
 <blockquote>
     A configuration describes the conditions in which the package has
@@ -1497,5 +1519,5 @@
  between machines running different operating
     systems, or when a project has to be deployed on several sites.
-<hr><h3><a name="Describing a configuration"></a><a href="#index"><tt>11.&nbsp;1</tt></a> - Describing a configuration</h3>
+<hr><h3><a name="Describing a configuration"></a><a href="#index"><tt>10.&nbsp;1</tt></a> - Describing a configuration</h3>
 <blockquote>
   <p><tt>CMT</tt>
@@ -1699,5 +1721,5 @@
 </ol>
 </blockquote>
-<hr><h3><a name="Defining the user tags"></a><a href="#index"><tt>11.&nbsp;2</tt></a> - Defining the user tags</h3>
+<hr><h3><a name="Defining the user tags"></a><a href="#index"><tt>10.&nbsp;2</tt></a> - Defining the user tags</h3>
 <blockquote>
   <p>The user configuration tags can generally be specified though
@@ -1765,5 +1787,5 @@
 </ul>
 </blockquote>
-<hr><h3><a name="Activating tags"></a><a href="#index"><tt>11.&nbsp;3</tt></a> - Activating tags</h3>
+<hr><h3><a name="Activating tags"></a><a href="#index"><tt>10.&nbsp;3</tt></a> - Activating tags</h3>
 <blockquote>
       By default, <tt>CMTCONFIG</tt>
@@ -1911,5 +1933,5 @@
 </blockquote>
 </blockquote>
-<hr><h2><a name="Working on a package"></a><a href="#index"><tt>12</tt></a> - Working on a package</h2>
+<hr><h2><a name="Working on a package"></a><a href="#index"><tt>11</tt></a> - Working on a package</h2>
 <blockquote>
   <p>In this section, we'll see, through a quite simple scenario,
@@ -1918,5 +1940,5 @@
    of the <tt>Foo</tt>
     package already used in this document. </p>
-<hr><h3><a name="Working on a library"></a><a href="#index"><tt>12.&nbsp;1</tt></a> - Working on a library</h3>
+<hr><h3><a name="Working on a library"></a><a href="#index"><tt>11.&nbsp;1</tt></a> - Working on a library</h3>
 <blockquote>
   <p>Let's assume, as a first example, that the <tt>Foo</tt>
@@ -2066,5 +2088,5 @@
       operation</p>
 </blockquote>
-<hr><h3><a name="Working on an application"></a><a href="#index"><tt>12.&nbsp;2</tt></a> - Working on an application</h3>
+<hr><h3><a name="Working on an application"></a><a href="#index"><tt>11.&nbsp;2</tt></a> - Working on an application</h3>
 <blockquote>
   <p>Assume we now want to add a test program to our
@@ -2151,5 +2173,5 @@
 </ul>
 </blockquote>
-<hr><h3><a name="Working on a test or external application"></a><a href="#index"><tt>12.&nbsp;3</tt></a> - Working on a test or external application</h3>
+<hr><h3><a name="Working on a test or external application"></a><a href="#index"><tt>11.&nbsp;3</tt></a> - Working on a test or external application</h3>
 <blockquote>
       It is also possible to work on a <i>test</i>
@@ -2178,78 +2200,6 @@
       interface are still available in these conditions. </p>
 </blockquote>
-<hr><h3><a name="Construction of a global environment"></a><a href="#index"><tt>12.&nbsp;4</tt></a> - Construction of a global environment</h3>
-<blockquote>
-  <p>A software base generally consists in many <i>packages</i>
-  ,
-        some of them providing <i>libraries</i>
-   or <i>documents</i>
-  ,
-        others providing <i>applications</i>
-  , some providing both, some
-        providing just <i>glues</i>
-   towards external software
-      products.</p>
-  <p> On another view, this software base may a mix of packages
-        shared between several projects and sets of packages specific to
-        various projects. One may have several software bases as well
-        (combined using the <tt>CMTPATH</tt>
- environment variable). </p>
-  <p> In such contexts, it is often desirable that a given project
-        defines its own selection of all existing packages. This can
-        easily be done with <tt>CMT</tt>
-   by defining a <i>project</i>
-        package, containing only <tt>use</tt>
-   statements towards the
-        appropriate selection of packages for this particular
-      project. </p>
-  <p>Let's consider as an example the project named
-  <tt>MyProject</tt>
-  . We may create the package named
-  <tt>MyProject</tt>
- similarly to any other package : </p>
-<pre>
-csh&gt; cd ..... 
-csh&gt; cmt create MyProject v1 /ProjectB</pre>
-  <p> Then the <tt>&nbsp;<a HREF='#The requirements file'>requirements</a>&nbsp;</tt>
-   file of this new package
-        will simply contain a set of <tt>use</tt>
-   statements, defining the
-  <i>official</i>
-   set of validated versions of the packages
-        required for the project. This mechanism also represents the
-        notion of <i>global release</i>
-   traditionally addressed in
-      configuration management environments </p>
-<pre class="cmt">
-package MyProject 
-
-use Cm v7r6 
-use Db v4r3 
-use El v4r2 
-use Su v5 
-use DbUI v1r2 Db 
-use ElUI v1r1 El 
-use VSUUI v3  Su/VSU 
-use VMM   v1 
-use VPC   v3 </pre>
-  <p>Then any user wanting to access the so-called <i>official</i>
-        release of the package set appropriate to the project
-  <tt>MyProject</tt>
-   will simply do (typically within its login
-      shell script) : </p>
-<pre>
-# a login script 
-
-... 
-
-source /ProjectB/MyProject/v1/cmt/setup.csh </pre>
-  <p>Later on, future evolutions of the <tt>MyProject</tt>
-   package
-        will reflect progressive integration steps, which
-  <i>validate</i>
- the evolutions of each referenced package. </p>
-</blockquote>
-</blockquote>
-<hr><h2><a name="Defining a document generator"></a><a href="#index"><tt>13</tt></a> - Defining a document generator</h2>
+</blockquote>
+<hr><h2><a name="Defining a document generator"></a><a href="#index"><tt>12</tt></a> - Defining a document generator</h2>
 <blockquote>
   <p> In a Unix environment, documents are built using <tt>make</tt>
@@ -2312,5 +2262,5 @@
       containing one main target. Both the resulting make fragment and
     the make target will have the name of the constituent.</p>
-<hr><h3><a name="An example : the tex document-style"></a><a href="#index"><tt>13.&nbsp;1</tt></a> - An example : the tex document-style</h3>
+<hr><h3><a name="An example : the tex document-style"></a><a href="#index"><tt>12.&nbsp;1</tt></a> - An example : the tex document-style</h3>
 <blockquote>
   <p>
@@ -2440,5 +2390,5 @@
 </ul>
 </blockquote>
-<hr><h3><a name="How to create and install a new document style"></a><a href="#index"><tt>13.&nbsp;2</tt></a> - How to create and install a new document style</h3>
+<hr><h3><a name="How to create and install a new document style"></a><a href="#index"><tt>12.&nbsp;2</tt></a> - How to create and install a new document style</h3>
 <blockquote>
 <blockquote><hr>
@@ -2463,5 +2413,5 @@
             same subdirectory, one of them will be the <i>header</i>
      of
-            the generated complete fragment, the other will be its
+     the generated complete fragment, the other will be its
     <i>trailer</i>
   </li>
@@ -2594,5 +2544,5 @@
 </center>
 </blockquote>
-<hr><h3><a name="Examples"></a><a href="#index"><tt>13.&nbsp;3</tt></a> - Examples</h3>
+<hr><h3><a name="Examples"></a><a href="#index"><tt>12.&nbsp;3</tt></a> - Examples</h3>
 <blockquote>
   <ol>
@@ -2651,5 +2601,5 @@
 </blockquote>
 </blockquote>
-<hr><h2><a name="The tools provided by CMT"></a><a href="#index"><tt>14</tt></a> - The tools provided by CMT</h2>
+<hr><h2><a name="The tools provided by CMT"></a><a href="#index"><tt>13</tt></a> - The tools provided by CMT</h2>
 <blockquote>
         The set of conventions and tools provided by <tt>CMT</tt>
@@ -2685,7 +2635,7 @@
             commands available through the <tt>cmt</tt>
  user interface. </p>
-<hr><h3><a name="The requirements file"></a><a href="#index"><tt>14.&nbsp;1</tt></a> - The requirements file</h3>
-<blockquote>
-<hr><h4><a name="The general requirements syntax"></a><a href="#index"><tt>14.&nbsp;1.&nbsp;1</tt></a> - The general requirements syntax</h4>
+<hr><h3><a name="The requirements file"></a><a href="#index"><tt>13.&nbsp;1</tt></a> - The requirements file</h3>
+<blockquote>
+<hr><h4><a name="The general requirements syntax"></a><a href="#index"><tt>13.&nbsp;1.&nbsp;1</tt></a> - The general requirements syntax</h4>
 <blockquote>
   <ul>
@@ -2701,5 +2651,5 @@
                       by space characters).</p>
       <p>Each statement is composed of words separated with spaces
-               or tabulations.</p>
+                      or tabulations.</p>
       <p>The first word of a statement is the name of the
                       configuration parameter.</p>
@@ -2752,5 +2702,5 @@
       <p>Comments : they start with the <tt>#</tt>
        character and 
-                  extend up to the end of the current line. 
+                        extend up to the end of the current line. 
     </p>
   </li>
@@ -2760,19 +2710,19 @@
 </blockquote>
 </blockquote>
-<hr><h3><a name="The concepts handled in the requirements file"></a><a href="#index"><tt>14.&nbsp;2</tt></a> - The concepts handled in the requirements file</h3>
-<blockquote>
-<hr><h4><a name="The package structuring style "></a><a href="#index"><tt>14.&nbsp;2.&nbsp;1</tt></a> - The package structuring style </h4>
-<blockquote>
-</blockquote>
-<hr><h4><a name="Meta-information : author, manager"></a><a href="#index"><tt>14.&nbsp;2.&nbsp;2</tt></a> - Meta-information : author, manager</h4>
+<hr><h3><a name="The concepts handled in the requirements file"></a><a href="#index"><tt>13.&nbsp;2</tt></a> - The concepts handled in the requirements file</h3>
+<blockquote>
+<hr><h4><a name="The package structuring style "></a><a href="#index"><tt>13.&nbsp;2.&nbsp;1</tt></a> - The package structuring style </h4>
+<blockquote>
+</blockquote>
+<hr><h4><a name="Meta-information : author, manager"></a><a href="#index"><tt>13.&nbsp;2.&nbsp;2</tt></a> - Meta-information : author, manager</h4>
 <blockquote>
             The author and manager names 
 </blockquote>
-<hr><h4><a name="package, version"></a><a href="#index"><tt>14.&nbsp;2.&nbsp;3</tt></a> - package, version</h4>
+<hr><h4><a name="package, version"></a><a href="#index"><tt>13.&nbsp;2.&nbsp;3</tt></a> - package, version</h4>
 <blockquote>
             The package name and version. These statements are purely
             informational.
 </blockquote>
-<hr><h4><a name="Constituents : application, library, document"></a><a href="#index"><tt>14.&nbsp;2.&nbsp;4</tt></a> - Constituents : application, library, document</h4>
+<hr><h4><a name="Constituents : application, library, document"></a><a href="#index"><tt>13.&nbsp;2.&nbsp;4</tt></a> - Constituents : application, library, document</h4>
 <blockquote>
   <p>Describe the composition of a constituent. Application
@@ -3034,5 +2984,5 @@
 </ol>
 </blockquote>
-<hr><h4><a name="Groups"></a><a href="#index"><tt>14.&nbsp;2.&nbsp;5</tt></a> - Groups</h4>
+<hr><h4><a name="Groups"></a><a href="#index"><tt>13.&nbsp;2.&nbsp;5</tt></a> - Groups</h4>
 <blockquote>
             Groups permit the organization of the constituents that must
@@ -3053,5 +3003,5 @@
                 features, graphical libraries) and therefore might require a
                 controled re-build. This is especially useful for having these
-                constituents only rebuilt on demand rather than rebuilt
+      constituents only rebuilt on demand rather than rebuilt
               automatically when the default make command is run.</p>
 <p>One could, for instance specify within the requirements file :</p>
@@ -3083,5 +3033,5 @@
  related constituents.</p>
 </blockquote>
-<hr><h4><a name="Languages"></a><a href="#index"><tt>14.&nbsp;2.&nbsp;6</tt></a> - Languages</h4>
+<hr><h4><a name="Languages"></a><a href="#index"><tt>13.&nbsp;2.&nbsp;6</tt></a> - Languages</h4>
 <blockquote>
             Some computer languages are known by default by <tt>CMT</tt>
@@ -3179,5 +3129,5 @@
 .
 </blockquote>
-<hr><h4><a name="Symbols"></a><a href="#index"><tt>14.&nbsp;2.&nbsp;7</tt></a> - Symbols</h4>
+<hr><h4><a name="Symbols"></a><a href="#index"><tt>13.&nbsp;2.&nbsp;7</tt></a> - Symbols</h4>
 <blockquote>
   <p>This is a generic concept supporting the notion of
@@ -3553,5 +3503,5 @@
       VisualC         "link.exe /nologo /machine:IX86 "
 </pre>
-<hr><h5><a name="actions"></a><a href="#index"><tt>14.&nbsp;2.&nbsp;7.&nbsp;1</tt></a> - actions</h5>
+<hr><h5><a name="actions"></a><a href="#index"><tt>13.&nbsp;2.&nbsp;7.&nbsp;1</tt></a> - actions</h5>
 <blockquote>
               Actions are one of the possible symbols. Their
@@ -3627,5 +3577,5 @@
 </blockquote>
 </blockquote>
-<hr><h4><a name="use"></a><a href="#index"><tt>14.&nbsp;2.&nbsp;8</tt></a> - use</h4>
+<hr><h4><a name="use"></a><a href="#index"><tt>13.&nbsp;2.&nbsp;8</tt></a> - use</h4>
 <blockquote>
   <p>Describe the relationships with other packages; the
@@ -3714,5 +3664,5 @@
 </ul>
 </blockquote>
-<hr><h4><a name="patterns"></a><a href="#index"><tt>14.&nbsp;2.&nbsp;9</tt></a> - patterns</h4>
+<hr><h4><a name="patterns"></a><a href="#index"><tt>13.&nbsp;2.&nbsp;9</tt></a> - patterns</h4>
 <blockquote>
   <p>Often, similar configuration items are needed over a
@@ -3831,5 +3781,5 @@
   <p>Then, in addition, user defined templates can be installed
                 within the pattern definitions. Their actual value will be
-              provided as arguments to the apply_pattern statement.</p>
+provided as arguments to the apply_pattern statement.</p>
   <p>User defined templates that have not been assigned a
               value when the pattern is applied are simply ignored
@@ -3842,5 +3792,5 @@
       <tt>${&lt;package&gt;_root}/src</tt>
       . However, often projects
-                need to override this default convention, and typical
+                        need to override this default convention, and typical
                         example is to set it to a branch named with the package
                         name. This convention is easily applied by defining a
@@ -3881,5 +3831,5 @@
     <p>Installing a systematic test application in all packages</p>
       <p>Quality assurance requirements might specify that every
-            package should provide a test program. One way to enforce
+                        package should provide a test program. One way to enforce
                         this is to build a global pattern declaring this
                         application. Then every make command would naturally
@@ -3893,5 +3843,5 @@
   </li>
 </ol>
-<hr><h5><a name="Applying a pattern"></a><a href="#index"><tt>14.&nbsp;2.&nbsp;9.&nbsp;1</tt></a> - Applying a pattern</h5>
+<hr><h5><a name="Applying a pattern"></a><a href="#index"><tt>13.&nbsp;2.&nbsp;9.&nbsp;1</tt></a> - Applying a pattern</h5>
 <blockquote>
               According to whether the <tt>-global</tt>
@@ -3958,5 +3908,5 @@
 </blockquote>
 </blockquote>
-<hr><h4><a name="cmtpath_patterns"></a><a href="#index"><tt>14.&nbsp;2.10</tt></a> - cmtpath_patterns</h4>
+<hr><h4><a name="cmtpath_patterns"></a><a href="#index"><tt>13.&nbsp;2.10</tt></a> - cmtpath_patterns</h4>
 <blockquote>
   <p>These patterns act quite similarly to the <i>global</i>
@@ -4005,5 +3955,5 @@
 </p>
 </blockquote>
-<hr><h4><a name="branches"></a><a href="#index"><tt>14.&nbsp;2.11</tt></a> - branches</h4>
+<hr><h4><a name="branches"></a><a href="#index"><tt>13.&nbsp;2.11</tt></a> - branches</h4>
 <blockquote>
   <p>Describe the specific directory branches to be added while
@@ -4020,5 +3970,5 @@
 .</p>
 </blockquote>
-<hr><h4><a name="Strategy specifications"></a><a href="#index"><tt>14.&nbsp;2.12</tt></a> - Strategy specifications</h4>
+<hr><h4><a name="Strategy specifications"></a><a href="#index"><tt>13.&nbsp;2.12</tt></a> - Strategy specifications</h4>
 <blockquote>
   <p>Users can control the behaviour of <tt>CMT</tt>
@@ -4141,5 +4091,5 @@
 &lt;project&gt;_no_cleanup</pre>
 </blockquote>
-<hr><h4><a name="setup_script, cleanup_script"></a><a href="#index"><tt>14.&nbsp;2.13</tt></a> - setup_script, cleanup_script</h4>
+<hr><h4><a name="setup_script, cleanup_script"></a><a href="#index"><tt>13.&nbsp;2.13</tt></a> - setup_script, cleanup_script</h4>
 <blockquote>
   <p>Specify user defined configuration scripts, which will be
@@ -4167,5 +4117,5 @@
 ).</p>
 </blockquote>
-<hr><h4><a name="include_path"></a><a href="#index"><tt>14.&nbsp;2.14</tt></a> - include_path</h4>
+<hr><h4><a name="include_path"></a><a href="#index"><tt>13.&nbsp;2.14</tt></a> - include_path</h4>
 <blockquote>
   <p>Override the specification for the default include search
@@ -4185,9 +4135,9 @@
  instead).</p>
 </blockquote>
-<hr><h4><a name="include_dirs"></a><a href="#index"><tt>14.&nbsp;2.15</tt></a> - include_dirs</h4>
+<hr><h4><a name="include_dirs"></a><a href="#index"><tt>13.&nbsp;2.15</tt></a> - include_dirs</h4>
 <blockquote>
 <p>Add explicit specifications for include access paths.</p>
 </blockquote>
-<hr><h4><a name="make_fragment"></a><a href="#index"><tt>14.&nbsp;2.16</tt></a> - make_fragment</h4>
+<hr><h4><a name="make_fragment"></a><a href="#index"><tt>13.&nbsp;2.16</tt></a> - make_fragment</h4>
 <blockquote>
   <p>This statement specifies a specialized makefile fragment,
@@ -4267,5 +4217,5 @@
                 of language definitions (C, C++, Fortran, Java, Lex, Yacc)
                 is provided by CMT itself but it is expected that projects
-             add new languages according to their needs. Event if the
+                add new languages according to their needs. Event if the
                 make fragment meant to be the implementation of a language
                 support is declared, the language support itself must be
@@ -4333,5 +4283,5 @@
 </p>
 </blockquote>
-<hr><h4><a name="public, private"></a><a href="#index"><tt>14.&nbsp;2.17</tt></a> - public, private</h4>
+<hr><h4><a name="public, private"></a><a href="#index"><tt>13.&nbsp;2.17</tt></a> - public, private</h4>
 <blockquote>
   <p>The <tt>public</tt>
@@ -4367,5 +4317,5 @@
   	    the sub-trees whether they are public or private (in order
 	    to ensure the hierarchy dependencies)</p>
-<hr><h5><a name="Scoping sections"></a><a href="#index"><tt>14.&nbsp;2.17.&nbsp;1</tt></a> - Scoping sections</h5>
+<hr><h5><a name="Scoping sections"></a><a href="#index"><tt>13.&nbsp;2.17.&nbsp;1</tt></a> - Scoping sections</h5>
 <blockquote>
               By using the <tt>public</tt>
@@ -4427,5 +4377,5 @@
 </blockquote>
 </blockquote>
-<hr><h4><a name="tag, apply_tag"></a><a href="#index"><tt>14.&nbsp;2.18</tt></a> - tag, apply_tag</h4>
+<hr><h4><a name="tag, apply_tag"></a><a href="#index"><tt>13.&nbsp;2.18</tt></a> - tag, apply_tag</h4>
 <blockquote>
   <p>The <tt>tag</tt>
@@ -4478,5 +4428,5 @@
 </blockquote>
 </blockquote>
-<hr><h3><a name="The general cmt user interface"></a><a href="#index"><tt>14.&nbsp;3</tt></a> - The general cmt user interface</h3>
+<hr><h3><a name="The general cmt user interface"></a><a href="#index"><tt>13.&nbsp;3</tt></a> - The general cmt user interface</h3>
 <blockquote>
           This utility (a shell script combined with a <tt>C++</tt>
@@ -4518,5 +4468,5 @@
    config                  : generate setup and cleanup scripts
    create &lt;package&gt; &lt;version&gt; [&lt;path&gt;] : create and configure a new package
-   create_project &lt;project&gt;  : create and configure a new project
+   create_project &lt;project&gt; &lt;name&gt; [&lt;path&gt;] : create and configure a new project
    cvsbranches &lt;module&gt;      : display the subdirectories for a module
    cvssubpackagess &lt;module&gt;  : display the subpackages for a module
@@ -4598,5 +4548,5 @@
    -no_cleanup             : inhibit install area cleanup</font></i></pre>
 <p>The following sections present the detail of each available command. </p>
-<hr><h4><a name="cmt broadcast"></a><a href="#index"><tt>14.&nbsp;3.&nbsp;1</tt></a> - cmt broadcast</h4>
+<hr><h4><a name="cmt broadcast"></a><a href="#index"><tt>13.&nbsp;3.&nbsp;1</tt></a> - cmt broadcast</h4>
 <blockquote>
             This command tries to repeatedly execute a shell command in the 
@@ -4663,5 +4613,5 @@
    list</li>
 </ol>
-<hr><h5><a name="Specifying the shell command"></a><a href="#index"><tt>14.&nbsp;3.&nbsp;1.&nbsp;1</tt></a> - Specifying the shell command</h5>
+<hr><h5><a name="Specifying the shell command"></a><a href="#index"><tt>13.&nbsp;3.&nbsp;1.&nbsp;1</tt></a> - Specifying the shell command</h5>
 <blockquote>
   <p>A priori any Unix or DOS shell command can be specified
@@ -4680,5 +4630,5 @@
 	    sometimes useful to have two levels of quotes</p>
 </blockquote>
-<hr><h5><a name="Templates in the shell command"></a><a href="#index"><tt>14.&nbsp;3.&nbsp;1.&nbsp;2</tt></a> - Templates in the shell command</h5>
+<hr><h5><a name="Templates in the shell command"></a><a href="#index"><tt>13.&nbsp;3.&nbsp;1.&nbsp;2</tt></a> - Templates in the shell command</h5>
 <blockquote>
   <p>Similarly to what exists in the <a href="#patterns">pattern</a>
@@ -4747,5 +4697,5 @@
 </blockquote>
 </blockquote>
-<hr><h4><a name="cmt build &lt;option&gt;"></a><a href="#index"><tt>14.&nbsp;3.&nbsp;2</tt></a> - cmt build &lt;option&gt;</h4>
+<hr><h4><a name="cmt build &lt;option&gt;"></a><a href="#index"><tt>13.&nbsp;3.&nbsp;2</tt></a> - cmt build &lt;option&gt;</h4>
 <blockquote>
   <p>The actions associated with the build options are
@@ -4802,5 +4752,5 @@
        for Unix environments. The main makefile is
                         expected to be named <tt>NMake</tt>
-      and the standard header
+       and the standard header
                         is named <tt>NMakefile.header</tt>
     </p>
@@ -4836,5 +4786,5 @@
     <li><tt>msdev</tt>
       <p>This command generates workspace (.dsw) and project 
-                      (.dsp) files required for the MSDev tool. </p>
+     (.dsp) files required for the MSDev tool. </p>
   </li>
     <li><tt>vsnet</tt>
@@ -4878,5 +4828,5 @@
                         using the <tt>build_strategy</tt>
        cmt statement, providing 
-                      either the "prototypes" or the "no_prototypes" values. </p>
+               either the "prototypes" or the "no_prototypes" values. </p>
       <p>In addition, any constituent may locally override this 
                         strategy using the "-prototypes" or "-no_prototypes" 
@@ -4904,5 +4854,5 @@
 </ul>
 </blockquote>
-<hr><h4><a name="cmt check configuration"></a><a href="#index"><tt>14.&nbsp;3.&nbsp;3</tt></a> - cmt check configuration</h4>
+<hr><h4><a name="cmt check configuration"></a><a href="#index"><tt>13.&nbsp;3.&nbsp;3</tt></a> - cmt check configuration</h4>
 <blockquote>
             This command reads the hierarchy of requirements files 
@@ -4911,5 +4861,5 @@
 <p>An empty output means that everything is fine. </p>
 </blockquote>
-<hr><h4><a name="cmt check files &lt;reference-file&gt; &lt;new-file&gt;"></a><a href="#index"><tt>14.&nbsp;3.&nbsp;4</tt></a> - cmt check files &lt;reference-file&gt; &lt;new-file&gt;</h4>
+<hr><h4><a name="cmt check files &lt;reference-file&gt; &lt;new-file&gt;"></a><a href="#index"><tt>13.&nbsp;3.&nbsp;4</tt></a> - cmt check files &lt;reference-file&gt; &lt;new-file&gt;</h4>
 <blockquote>
             This command compares the reference file to the new file, and 
@@ -4920,7 +4870,7 @@
 ) is produced. </p>
 </blockquote>
-<hr><h4><a name="cmt checkout ..."></a><a href="#index"><tt>14.&nbsp;3.&nbsp;5</tt></a> - cmt checkout ...</h4>
-<blockquote>
-            See the <a href="#Using cvs together with CMT">paragraph</a>
+<hr><h4><a name="cmt checkout ..."></a><a href="#index"><tt>13.&nbsp;3.&nbsp;5</tt></a> - cmt checkout ...</h4>
+<blockquote>
+        See the <a href="#Using cvs together with CMT">paragraph</a>
             on how to use cvs together with <tt>CMT</tt>
 , and more specifically the
@@ -4928,10 +4878,10 @@
 .
 </blockquote>
-<hr><h4><a name="cmt co ..."></a><a href="#index"><tt>14.&nbsp;3.&nbsp;6</tt></a> - cmt co ...</h4>
+<hr><h4><a name="cmt co ..."></a><a href="#index"><tt>13.&nbsp;3.&nbsp;6</tt></a> - cmt co ...</h4>
 <blockquote>
             This is simply a short cut to the <tt>cmt checkout</tt>
  command. 
 </blockquote>
-<hr><h4><a name="cmt cleanup [-csh|-sh]"></a><a href="#index"><tt>14.&nbsp;3.&nbsp;7</tt></a> - cmt cleanup [-csh|-sh]</h4>
+<hr><h4><a name="cmt cleanup [-csh|-sh]"></a><a href="#index"><tt>13.&nbsp;3.&nbsp;7</tt></a> - cmt cleanup [-csh|-sh]</h4>
 <blockquote>
             This command generates (to the standard output) a set of shell 
@@ -4943,5 +4893,5 @@
  command. </p>
 </blockquote>
-<hr><h4><a name="cmt config"></a><a href="#index"><tt>14.&nbsp;3.&nbsp;8</tt></a> - cmt config</h4>
+<hr><h4><a name="cmt config"></a><a href="#index"><tt>13.&nbsp;3.&nbsp;8</tt></a> - cmt config</h4>
 <blockquote>
   <p>This command (re-)generates the setup scripts and the
@@ -4983,5 +4933,5 @@
  are required any longer.</p>
 </blockquote>
-<hr><h4><a name="cmt create &lt;package&gt; &lt;version&gt; [&lt;area&gt;]"></a><a href="#index"><tt>14.&nbsp;3.&nbsp;9</tt></a> - cmt create &lt;package&gt; &lt;version&gt; [&lt;area&gt;]</h4>
+<hr><h4><a name="cmt create &lt;package&gt; &lt;version&gt; [&lt;area&gt;]"></a><a href="#index"><tt>13.&nbsp;3.&nbsp;9</tt></a> - cmt create &lt;package&gt; &lt;version&gt; [&lt;area&gt;]</h4>
 <blockquote>
   <p>
@@ -5006,5 +4956,5 @@
 </ul>
 </blockquote>
-<hr><h4><a name="cmt expand model [-strict] &lt;model-string&gt;"></a><a href="#index"><tt>14.&nbsp;3.10</tt></a> - cmt expand model [-strict] &lt;model-string&gt;</h4>
+<hr><h4><a name="cmt expand model [-strict] &lt;model-string&gt;"></a><a href="#index"><tt>13.&nbsp;3.10</tt></a> - cmt expand model [-strict] &lt;model-string&gt;</h4>
 <blockquote>
             This command produces on the standard output an
@@ -5136,5 +5086,5 @@
 </ul>
 </blockquote>
-<hr><h4><a name="cmt filter &lt;in-file&gt; &lt;out-file&gt;"></a><a href="#index"><tt>14.&nbsp;3.11</tt></a> - cmt filter &lt;in-file&gt; &lt;out-file&gt;</h4>
+<hr><h4><a name="cmt filter &lt;in-file&gt; &lt;out-file&gt;"></a><a href="#index"><tt>13.&nbsp;3.11</tt></a> - cmt filter &lt;in-file&gt; &lt;out-file&gt;</h4>
 <blockquote>
             This command reads &lt;in-file&gt;, substitutes all occurences 
@@ -5153,10 +5103,10 @@
               configuration files, etc... </p>
 </blockquote>
-<hr><h4><a name="cmt help | --help"></a><a href="#index"><tt>14.&nbsp;3.12</tt></a> - cmt help | --help</h4>
+<hr><h4><a name="cmt help | --help"></a><a href="#index"><tt>13.&nbsp;3.12</tt></a> - cmt help | --help</h4>
 <blockquote>
             This command shows the list of options of the <tt>cmt</tt>
  driver. 
 </blockquote>
-<hr><h4><a name="cmt lock [ &lt;package&gt; &lt;version&gt; [&lt;area&gt;] ]"></a><a href="#index"><tt>14.&nbsp;3.13</tt></a> - cmt lock [ &lt;package&gt; &lt;version&gt; [&lt;area&gt;] ]</h4>
+<hr><h4><a name="cmt lock [ &lt;package&gt; &lt;version&gt; [&lt;area&gt;] ]"></a><a href="#index"><tt>13.&nbsp;3.13</tt></a> - cmt lock [ &lt;package&gt; &lt;version&gt; [&lt;area&gt;] ]</h4>
 <blockquote>
             This command tries to set a lock onto the current package (or onto the
@@ -5183,5 +5133,5 @@
 </ol>
 </blockquote>
-<hr><h4><a name="cmt remove &lt;package&gt; &lt;version&gt; [&lt;area&gt;]"></a><a href="#index"><tt>14.&nbsp;3.14</tt></a> - cmt remove &lt;package&gt; &lt;version&gt; [&lt;area&gt;]</h4>
+<hr><h4><a name="cmt remove &lt;package&gt; &lt;version&gt; [&lt;area&gt;]"></a><a href="#index"><tt>13.&nbsp;3.14</tt></a> - cmt remove &lt;package&gt; &lt;version&gt; [&lt;area&gt;]</h4>
 <blockquote>
             This command removes one version of the specified package. If
@@ -5197,5 +5147,5 @@
               will be deleted.</p>
 </blockquote>
-<hr><h4><a name="cmt remove library_links"></a><a href="#index"><tt>14.&nbsp;3.15</tt></a> - cmt remove library_links</h4>
+<hr><h4><a name="cmt remove library_links"></a><a href="#index"><tt>13.&nbsp;3.15</tt></a> - cmt remove library_links</h4>
 <blockquote>
             This command removes symbolic links towards all imported
@@ -5206,5 +5156,5 @@
             when one runs <tt>gmake clean</tt>
 </blockquote>
-<hr><h4><a name="cmt run [shell-command]"></a><a href="#index"><tt>14.&nbsp;3.16</tt></a> - cmt run [shell-command]</h4>
+<hr><h4><a name="cmt run [shell-command]"></a><a href="#index"><tt>13.&nbsp;3.16</tt></a> - cmt run [shell-command]</h4>
 <blockquote>
             This command runs any shell command, in the context of the 
@@ -5226,5 +5176,5 @@
 	    to any package context. </p>
 </blockquote>
-<hr><h4><a name="cmt set version &lt;version&gt;"></a><a href="#index"><tt>14.&nbsp;3.17</tt></a> - cmt set version &lt;version&gt;</h4>
+<hr><h4><a name="cmt set version &lt;version&gt;"></a><a href="#index"><tt>13.&nbsp;3.17</tt></a> - cmt set version &lt;version&gt;</h4>
 <blockquote>
             This command creates and/or fills in the
@@ -5238,5 +5188,5 @@
 	    one CMT package.</p>
 </blockquote>
-<hr><h4><a name="cmt set versions"></a><a href="#index"><tt>14.&nbsp;3.18</tt></a> - cmt set versions</h4>
+<hr><h4><a name="cmt set versions"></a><a href="#index"><tt>13.&nbsp;3.18</tt></a> - cmt set versions</h4>
 <blockquote>
               This command applies recursively the <tt>cmt set version
@@ -5249,5 +5199,5 @@
  files</p>
 </blockquote>
-<hr><h4><a name="cmt setup [-csh|-sh|-bat]"></a><a href="#index"><tt>14.&nbsp;3.19</tt></a> - cmt setup [-csh|-sh|-bat]</h4>
+<hr><h4><a name="cmt setup [-csh|-sh|-bat]"></a><a href="#index"><tt>13.&nbsp;3.19</tt></a> - cmt setup [-csh|-sh|-bat]</h4>
 <blockquote>
             This command generates (to the standard output) a set of shell
@@ -5264,5 +5214,5 @@
  command.</p>
 </blockquote>
-<hr><h4><a name="cmt show &lt;option&gt;"></a><a href="#index"><tt>14.&nbsp;3.20</tt></a> - cmt show &lt;option&gt;</h4>
+<hr><h4><a name="cmt show &lt;option&gt;"></a><a href="#index"><tt>13.&nbsp;3.20</tt></a> - cmt show &lt;option&gt;</h4>
 <blockquote>
   <ul>
@@ -5320,5 +5270,5 @@
       <li><tt>groups</tt>
         <p>This command displays all groups possibly defined
-                    in constituents of the current package (using the
+                        in constituents of the current package (using the
           <tt>-group=&lt;<i>group-name</i>
         &gt;</tt>
@@ -5567,5 +5517,5 @@
 </ul>
 </blockquote>
-<hr><h4><a name="cmt system"></a><a href="#index"><tt>14.&nbsp;3.21</tt></a> - cmt system</h4>
+<hr><h4><a name="cmt system"></a><a href="#index"><tt>13.&nbsp;3.21</tt></a> - cmt system</h4>
 <blockquote>
             This command displays the current value assigned by default to 
@@ -5573,5 +5523,5 @@
  environment variable. 
 </blockquote>
-<hr><h4><a name="cmt unlock [ &lt;package&gt; &lt;version&gt; [&lt;area&gt;] ]"></a><a href="#index"><tt>14.&nbsp;3.22</tt></a> - cmt unlock [ &lt;package&gt; &lt;version&gt; [&lt;area&gt;] ]</h4>
+<hr><h4><a name="cmt unlock [ &lt;package&gt; &lt;version&gt; [&lt;area&gt;] ]"></a><a href="#index"><tt>13.&nbsp;3.22</tt></a> - cmt unlock [ &lt;package&gt; &lt;version&gt; [&lt;area&gt;] ]</h4>
 <blockquote>
             This command tries to remove a lock from the current package (or from the
@@ -5596,5 +5546,5 @@
 </p>
 </blockquote>
-<hr><h4><a name="cmt version | --version"></a><a href="#index"><tt>14.&nbsp;3.23</tt></a> - cmt version | --version</h4>
+<hr><h4><a name="cmt version | --version"></a><a href="#index"><tt>13.&nbsp;3.23</tt></a> - cmt version | --version</h4>
 <blockquote>
             This command shows the current verion of <tt>CMT</tt>
@@ -5604,5 +5554,5 @@
  sources. 
 </blockquote>
-<hr><h4><a name="cmt cvstags &lt;module&gt;"></a><a href="#index"><tt>14.&nbsp;3.24</tt></a> - cmt cvstags &lt;module&gt;</h4>
+<hr><h4><a name="cmt cvstags &lt;module&gt;"></a><a href="#index"><tt>13.&nbsp;3.24</tt></a> - cmt cvstags &lt;module&gt;</h4>
 <blockquote>
             (see the section on <i>how tu use </i>
@@ -5612,12 +5562,12 @@
  for more details on this command) 
 </blockquote>
-<hr><h4><a name="cmt cvsbranches &lt;module&gt;"></a><a href="#index"><tt>14.&nbsp;3.25</tt></a> - cmt cvsbranches &lt;module&gt;</h4>
-<blockquote>
-</blockquote>
-<hr><h4><a name="cmt cvssubpackages &lt;module&gt;"></a><a href="#index"><tt>14.&nbsp;3.26</tt></a> - cmt cvssubpackages &lt;module&gt;</h4>
-<blockquote>
-</blockquote>
-</blockquote>
-<hr><h3><a name="The setup and cleanup scripts"></a><a href="#index"><tt>14.&nbsp;4</tt></a> - The setup and cleanup scripts</h3>
+<hr><h4><a name="cmt cvsbranches &lt;module&gt;"></a><a href="#index"><tt>13.&nbsp;3.25</tt></a> - cmt cvsbranches &lt;module&gt;</h4>
+<blockquote>
+</blockquote>
+<hr><h4><a name="cmt cvssubpackages &lt;module&gt;"></a><a href="#index"><tt>13.&nbsp;3.26</tt></a> - cmt cvssubpackages &lt;module&gt;</h4>
+<blockquote>
+</blockquote>
+</blockquote>
+<hr><h3><a name="The setup and cleanup scripts"></a><a href="#index"><tt>13.&nbsp;4</tt></a> - The setup and cleanup scripts</h3>
 <blockquote>
           They are produced by the <tt>cmt config</tt>
@@ -5649,5 +5599,5 @@
                 the <tt>cmt setup</tt>
      utility into a temporary file and
-              running this temporary file.  </li>
+           running this temporary file.  </li>
     <li>
                   Activation of the user defined setup and cleanup scripts 
@@ -5669,5 +5619,5 @@
           development area. 
 </blockquote>
-<hr><h3><a name="cmt build prototype"></a><a href="#index"><tt>14.&nbsp;5</tt></a> - cmt build prototype</h3>
+<hr><h3><a name="cmt build prototype"></a><a href="#index"><tt>13.&nbsp;5</tt></a> - cmt build prototype</h3>
 <blockquote>
           This command is only provided for development of <tt>C</tt>
@@ -5711,5 +5661,5 @@
 </blockquote>
 </blockquote>
-<hr><h2><a name="Using cvs together with CMT"></a><a href="#index"><tt>15</tt></a> - Using cvs together with CMT</h2>
+<hr><h2><a name="Using cvs together with CMT"></a><a href="#index"><tt>14</tt></a> - Using cvs together with CMT</h2>
 <blockquote>
   <p>Nothing special is apriori required by <tt>CMT</tt>
@@ -5735,5 +5685,5 @@
   <a href="#The internal mechanism of cmt cvs operations">appendix</a>
 .</p>
-<hr><h3><a name="Importing a package into a cvs repository"></a><a href="#index"><tt>15.&nbsp;1</tt></a> - Importing a package into a cvs repository</h3>
+<hr><h3><a name="Importing a package into a cvs repository"></a><a href="#index"><tt>14.&nbsp;1</tt></a> - Importing a package into a cvs repository</h3>
 <blockquote>
   <p>Generally, everything composing a package (below the
@@ -5787,5 +5737,5 @@
  form. </p>
 </blockquote>
-<hr><h3><a name="Checking a package out from a cvs repository"></a><a href="#index"><tt>15.&nbsp;2</tt></a> - Checking a package out from a cvs repository</h3>
+<hr><h3><a name="Checking a package out from a cvs repository"></a><a href="#index"><tt>14.&nbsp;2</tt></a> - Checking a package out from a cvs repository</h3>
 <blockquote>
   <p>Assuming the previous conventions on module name and version
@@ -5814,5 +5764,5 @@
   </li>
     <li>
-          creating a base directory with the package name is mandatory 
+            creating a base directory with the package name is mandatory 
             here, and is <i>not</i>
      taken into account by <tt>cvs</tt>
@@ -5871,5 +5821,5 @@
 csh&gt; [g]make</pre>
 </blockquote>
-<hr><h3><a name="Querying CVS about some important infos"></a><a href="#index"><tt>15.&nbsp;3</tt></a> - Querying CVS about some important infos</h3>
+<hr><h3><a name="Querying CVS about some important infos"></a><a href="#index"><tt>14.&nbsp;3</tt></a> - Querying CVS about some important infos</h3>
 <blockquote>
     It is possible, using the commands :
@@ -5937,5 +5887,5 @@
 </ol>
 </blockquote>
-<hr><h3><a name="Working on a package, creating a new release"></a><a href="#index"><tt>15.&nbsp;4</tt></a> - Working on a package, creating a new release</h3>
+<hr><h3><a name="Working on a package, creating a new release"></a><a href="#index"><tt>14.&nbsp;4</tt></a> - Working on a package, creating a new release</h3>
 <blockquote>
   <p>This section presents the way to instanciate a new release of
@@ -5980,5 +5930,5 @@
 </ol>
 </blockquote>
-<hr><h3><a name="Getting a particular tagged version out of CVS"></a><a href="#index"><tt>15.&nbsp;5</tt></a> - Getting a particular tagged version out of CVS</h3>
+<hr><h3><a name="Getting a particular tagged version out of CVS"></a><a href="#index"><tt>14.&nbsp;5</tt></a> - Getting a particular tagged version out of CVS</h3>
 <blockquote>
   <p>The previous example presented the standard case where one gets
@@ -6008,5 +5958,5 @@
 </blockquote>
 </blockquote>
-<hr><h2><a name="Interfacing an external package with CMT"></a><a href="#index"><tt>16</tt></a> - Interfacing an external package with CMT</h2>
+<hr><h2><a name="Interfacing an external package with CMT"></a><a href="#index"><tt>15</tt></a> - Interfacing an external package with CMT</h2>
 <blockquote>
   <p>Very often, external packages (typically commercial products, or
@@ -6088,5 +6038,5 @@
           packages. </p>
 </blockquote>
-<hr><h2><a name="The installation area mechanism"></a><a href="#index"><tt>17</tt></a> - The installation area mechanism</h2>
+<hr><h2><a name="The installation area mechanism"></a><a href="#index"><tt>16</tt></a> - The installation area mechanism</h2>
 <blockquote>
   <p>CMT proposes and implements a flexible architecture for
@@ -6125,5 +6075,5 @@
       files, documentation and header files.</li>
 </ol>
-<hr><h3><a name="The default implementation"></a><a href="#index"><tt>17.&nbsp;1</tt></a> - The default implementation</h3>
+<hr><h3><a name="The default implementation"></a><a href="#index"><tt>16.&nbsp;1</tt></a> - The default implementation</h3>
 <blockquote>
 <p>It is provided in terms of</p>
@@ -6196,5 +6146,5 @@
     local patterns.</p>
 </blockquote>
-<hr><h3><a name="Tuning the installation area mechanisms"></a><a href="#index"><tt>17.&nbsp;2</tt></a> - Tuning the installation area mechanisms</h3>
+<hr><h3><a name="Tuning the installation area mechanisms"></a><a href="#index"><tt>16.&nbsp;2</tt></a> - Tuning the installation area mechanisms</h3>
 <blockquote>
   <p>First of all every individual sub-project may activate or
@@ -6275,5 +6225,5 @@
 </blockquote>
 </blockquote>
-<hr><h2><a name="Installing CMT for the first time"></a><a href="#index"><tt>18</tt></a> - Installing CMT for the first time</h2>
+<hr><h2><a name="Installing CMT for the first time"></a><a href="#index"><tt>17</tt></a> - Installing CMT for the first time</h2>
 <blockquote>
   <P>These sections are of interest only if <tt>CMT</tt>
@@ -6298,5 +6248,5 @@
             or operate <tt>CMT</tt>
 . </P>
-<hr><h3><a name="Installing CMT on your Unix site"></a><a href="#index"><tt>18.&nbsp;1</tt></a> - Installing CMT on your Unix site</h3>
+<hr><h3><a name="Installing CMT on your Unix site"></a><a href="#index"><tt>17.&nbsp;1</tt></a> - Installing CMT on your Unix site</h3>
 <blockquote>
   <P>The very first operation after dowloading <tt>CMT</tt>
@@ -6375,5 +6325,5 @@
 csh&gt; gmake</pre>
 </blockquote>
-<hr><h3><a name="Installing CMT on a Windows or Windows NT site"></a><a href="#index"><tt>18.&nbsp;2</tt></a> - Installing CMT on a Windows or Windows NT site</h3>
+<hr><h3><a name="Installing CMT on a Windows or Windows NT site"></a><a href="#index"><tt>17.&nbsp;2</tt></a> - Installing CMT on a Windows or Windows NT site</h3>
 <blockquote>
   <p>You first have to fetch the distribution kit from the Web at 
@@ -6427,7 +6377,7 @@
 </blockquote>
 </blockquote>
-<hr><h2><a name="Appendices"></a><a href="#index"><tt>19</tt></a> - Appendices</h2>
-<blockquote>
-<hr><h3><a name="Copyright"></a><a href="#index"><tt>19.&nbsp;1</tt></a> - Copyright</h3>
+<hr><h2><a name="Appendices"></a><a href="#index"><tt>18</tt></a> - Appendices</h2>
+<blockquote>
+<hr><h3><a name="Copyright"></a><a href="#index"><tt>18.&nbsp;1</tt></a> - Copyright</h3>
 <blockquote>
   <center><b>Copyright LAL and Christian Arnault LAL-Orsay CNRS</b>
@@ -6464,5 +6414,5 @@
 knowledge of the CeCILL license and that you accept its terms.</p>
 </blockquote>
-<hr><h3><a name="Standard make targets predefined in CMT"></a><a href="#index"><tt>19.&nbsp;2</tt></a> - Standard make targets predefined in CMT</h3>
+<hr><h3><a name="Standard make targets predefined in CMT"></a><a href="#index"><tt>18.&nbsp;2</tt></a> - Standard make targets predefined in CMT</h3>
 <blockquote>
 <p>These targets can always be listed through the following command : </p>
@@ -6527,5 +6477,5 @@
         <td>only build this 
                   particular component (as opposed to the <tt>all</tt>
-          target that tries to build all components of this 
+                  target that tries to build all components of this 
                 package)</td>
     </tr>
@@ -6544,7 +6494,7 @@
 sh&gt; gmake Foo </pre>
 </blockquote>
-<hr><h3><a name="Standard macros predefined in CMT"></a><a href="#index"><tt>19.&nbsp;3</tt></a> - Standard macros predefined in CMT</h3>
-<blockquote>
-<hr><h4><a name="CMT static macros"></a><a href="#index"><tt>19.&nbsp;3.&nbsp;1</tt></a> - CMT static macros</h4>
+<hr><h3><a name="Standard macros predefined in CMT"></a><a href="#index"><tt>18.&nbsp;3</tt></a> - Standard macros predefined in CMT</h3>
+<blockquote>
+<hr><h4><a name="CMT static macros"></a><a href="#index"><tt>18.&nbsp;3.&nbsp;1</tt></a> - CMT static macros</h4>
 <blockquote>
     These macros provide static data about CMT itself. They cannot be
@@ -6583,5 +6533,5 @@
 </p>
 </blockquote>
-<hr><h4><a name="Structural macros"></a><a href="#index"><tt>19.&nbsp;3.&nbsp;2</tt></a> - Structural macros</h4>
+<hr><h4><a name="Structural macros"></a><a href="#index"><tt>18.&nbsp;3.&nbsp;2</tt></a> - Structural macros</h4>
 <blockquote>
     These macros describe the structural conventions followed by
@@ -6674,5 +6624,5 @@
         <td><tt>cmt_compiler_version</tt>
       </td>
-      <td>the version of the currently visible C++ compiler </td>
+      <td>the version of the currently visible C++ compiler</td>
         <td><tt>&lt;none&gt;</tt>
       </td>
@@ -6681,5 +6631,5 @@
 </p>
 </blockquote>
-<hr><h4><a name="Language related macros"></a><a href="#index"><tt>19.&nbsp;3.&nbsp;3</tt></a> - Language related macros</h4>
+<hr><h4><a name="Language related macros"></a><a href="#index"><tt>18.&nbsp;3.&nbsp;3</tt></a> - Language related macros</h4>
 <blockquote>
     These macros are purely conventional. They are expected in the
@@ -6933,5 +6883,5 @@
 </p>
 </blockquote>
-<hr><h4><a name="Package customizing macros"></a><a href="#index"><tt>19.&nbsp;3.&nbsp;4</tt></a> - Package customizing macros</h4>
+<hr><h4><a name="Package customizing macros"></a><a href="#index"><tt>18.&nbsp;3.&nbsp;4</tt></a> - Package customizing macros</h4>
 <blockquote>
     These macros do not receive default values. They are all prefixed
@@ -7091,10 +7041,10 @@
         <td>specifies the base location for external software
                   described in glue packages. This macro is generally used to
-               specify the previous one</td>
+                specify the previous one</td>
     </tr>
   </table>
 </p>
 </blockquote>
-<hr><h4><a name="Constituent specific customizing macros"></a><a href="#index"><tt>19.&nbsp;3.&nbsp;5</tt></a> - Constituent specific customizing macros</h4>
+<hr><h4><a name="Constituent specific customizing macros"></a><a href="#index"><tt>18.&nbsp;3.&nbsp;5</tt></a> - Constituent specific customizing macros</h4>
 <blockquote>
     These macros do not receive any default values (ie they are empty
@@ -7165,5 +7115,5 @@
         &gt;_linkopts</tt>
          macro, which
-                provides exported linker options required by clients
+                    provides exported linker options required by clients
                     packages to use the package libraries.
       </td>
@@ -7204,5 +7154,5 @@
       </td>
         <td>
-                    provides user defined dependency specifications for each
+            provides user defined dependency specifications for each
                     group. The typical use of this macro is fill it
                     with the name of the list of some other constituents
@@ -7217,5 +7167,5 @@
 </p>
 </blockquote>
-<hr><h4><a name="Source specific customizing macros"></a><a href="#index"><tt>19.&nbsp;3.&nbsp;6</tt></a> - Source specific customizing macros</h4>
+<hr><h4><a name="Source specific customizing macros"></a><a href="#index"><tt>18.&nbsp;3.&nbsp;6</tt></a> - Source specific customizing macros</h4>
 <blockquote>
     These macros do not receive any default values (ie they are empty
@@ -7257,5 +7207,5 @@
 </p>
 </blockquote>
-<hr><h4><a name="Generated macros"></a><a href="#index"><tt>19.&nbsp;3.&nbsp;7</tt></a> - Generated macros</h4>
+<hr><h4><a name="Generated macros"></a><a href="#index"><tt>18.&nbsp;3.&nbsp;7</tt></a> - Generated macros</h4>
 <blockquote>
   <p> These macros are automatically <i>generated</i>
@@ -7451,5 +7401,5 @@
 </p>
 </blockquote>
-<hr><h4><a name="Macros related with the installation area mechanisms"></a><a href="#index"><tt>19.&nbsp;3.&nbsp;8</tt></a> - Macros related with the installation area mechanisms</h4>
+<hr><h4><a name="Macros related with the installation area mechanisms"></a><a href="#index"><tt>18.&nbsp;3.&nbsp;8</tt></a> - Macros related with the installation area mechanisms</h4>
 <blockquote>
     These macros contain the parameterisation of the installation area
@@ -7557,5 +7507,5 @@
 </p>
 </blockquote>
-<hr><h4><a name="Utility macros"></a><a href="#index"><tt>19.&nbsp;3.&nbsp;9</tt></a> - Utility macros</h4>
+<hr><h4><a name="Utility macros"></a><a href="#index"><tt>18.&nbsp;3.&nbsp;9</tt></a> - Utility macros</h4>
 <blockquote>
     These macros are used to specify the behaviour of various actions
@@ -7702,5 +7652,5 @@
 </blockquote>
 </blockquote>
-<hr><h3><a name="Standard tags generated by CMT"></a><a href="#index"><tt>19.&nbsp;4</tt></a> - Standard tags generated by CMT</h3>
+<hr><h3><a name="Standard tags generated by CMT"></a><a href="#index"><tt>18.&nbsp;4</tt></a> - Standard tags generated by CMT</h3>
 <blockquote>
   <p>
@@ -7809,5 +7759,5 @@
 </p>
 </blockquote>
-<hr><h3><a name="Standard templates for makefile fragments"></a><a href="#index"><tt>19.&nbsp;5</tt></a> - Standard templates for makefile fragments</h3>
+<hr><h3><a name="Standard templates for makefile fragments"></a><a href="#index"><tt>18.&nbsp;5</tt></a> - Standard templates for makefile fragments</h3>
 <blockquote>
   <p>
@@ -7952,5 +7902,5 @@
 </p>
 </blockquote>
-<hr><h3><a name="Makefile generation sequences"></a><a href="#index"><tt>19.&nbsp;6</tt></a> - Makefile generation sequences</h3>
+<hr><h3><a name="Makefile generation sequences"></a><a href="#index"><tt>18.&nbsp;6</tt></a> - Makefile generation sequences</h3>
 <blockquote>
 <blockquote><hr>
@@ -8071,5 +8021,5 @@
 </p>
 </blockquote>
-<hr><h3><a name="The complete requirements syntax"></a><a href="#index"><tt>19.&nbsp;7</tt></a> - The complete requirements syntax</h3>
+<hr><h3><a name="The complete requirements syntax"></a><a href="#index"><tt>18.&nbsp;7</tt></a> - The complete requirements syntax</h3>
 <blockquote>
   The syntax of specification statements that can be installed in a
@@ -9801,5 +9751,5 @@
 </center>
 </blockquote>
-<hr><h3><a name="The default strategies defined in CMT"></a><a href="#index"><tt>19.&nbsp;8</tt></a> - The default strategies defined in CMT</h3>
+<hr><h3><a name="The default strategies defined in CMT"></a><a href="#index"><tt>18.&nbsp;8</tt></a> - The default strategies defined in CMT</h3>
 <blockquote>
 <pre class="cmt">
@@ -9807,5 +9757,5 @@
   DefaultInstallAreaStrategy = WithoutInstallArea</pre>
 </blockquote>
-<hr><h3><a name="The internal mechanism of cmt cvs operations"></a><a href="#index"><tt>19.&nbsp;9</tt></a> - The internal mechanism of cmt cvs operations</h3>
+<hr><h3><a name="The internal mechanism of cmt cvs operations"></a><a href="#index"><tt>18.&nbsp;9</tt></a> - The internal mechanism of cmt cvs operations</h3>
 <blockquote>
   Generally, CVS does not handle queries upon the repository (such as
@@ -9910,8 +9860,16 @@
 <tr>
 <td width="100"><tt>&nbsp;4.&nbsp;1</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The project file">The project file</a></td>
+</tr>
+<tr>
+<td width="100"><tt>&nbsp;4.&nbsp;2</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Projects and strategies">Projects and strategies</a></td>
+</tr>
+<tr>
+<td width="100"><tt>&nbsp;4.&nbsp;3</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#CMTPROJECTPATH">CMTPROJECTPATH</a></td>
 </tr>
 <tr>
-<td width="100"><tt>&nbsp;4.&nbsp;2</tt></td>
+<td width="100"><tt>&nbsp;4.&nbsp;4</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#CMTPATH">CMTPATH</a></td>
 </tr>
@@ -9926,440 +9884,432 @@
 <tr>
 <td width="100"><tt>&nbsp;7</tt></td>
-<td><a href="#The concept of project">The concept of project</a></td>
+<td><a href="#Assigning semantics to packages. Common practices">Assigning semantics to packages. Common practices</a></td>
+</tr>
+<tr>
+<td width="100"><tt>&nbsp;7.&nbsp;1</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The primary package">The primary package</a></td>
+</tr>
+<tr>
+<td width="100"><tt>&nbsp;7.&nbsp;2</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The policy package">The policy package</a></td>
+</tr>
+<tr>
+<td width="100"><tt>&nbsp;7.&nbsp;3</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The container or management package">The container or management package</a></td>
+</tr>
+<tr>
+<td width="100"><tt>&nbsp;7.&nbsp;4</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The release package">The release package</a></td>
+</tr>
+<tr>
+<td width="100"><tt>&nbsp;7.&nbsp;5</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The glue or interface package">The glue or interface package</a></td>
 </tr>
 <tr>
 <td width="100"><tt>&nbsp;8</tt></td>
-<td><a href="#Assigning semantics to packages. Common practices">Assigning semantics to packages. Common practices</a></td>
-</tr>
-<tr>
-<td width="100"><tt>&nbsp;8.&nbsp;1</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The primary package">The primary package</a></td>
-</tr>
-<tr>
-<td width="100"><tt>&nbsp;8.&nbsp;2</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The policy package">The policy package</a></td>
-</tr>
-<tr>
-<td width="100"><tt>&nbsp;8.&nbsp;3</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The container or management package">The container or management package</a></td>
-</tr>
-<tr>
-<td width="100"><tt>&nbsp;8.&nbsp;4</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The release package">The release package</a></td>
-</tr>
-<tr>
-<td width="100"><tt>&nbsp;8.&nbsp;5</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The glue or interface package">The glue or interface package</a></td>
+<td><a href="#Managing site dependent features - The CMTSITE environment variable">Managing site dependent features - The CMTSITE environment variable</a></td>
 </tr>
 <tr>
 <td width="100"><tt>&nbsp;9</tt></td>
-<td><a href="#Managing site dependent features - The CMTSITE environment variable">Managing site dependent features - The CMTSITE environment variable</a></td>
+<td><a href="#Configuring a package">Configuring a package</a></td>
 </tr>
 <tr>
 <td width="100"><tt>10</tt></td>
-<td><a href="#Configuring a package">Configuring a package</a></td>
+<td><a href="#Selecting a specific configuration">Selecting a specific configuration</a></td>
+</tr>
+<tr>
+<td width="100"><tt>10.&nbsp;1</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Describing a configuration">Describing a configuration</a></td>
+</tr>
+<tr>
+<td width="100"><tt>10.&nbsp;2</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Defining the user tags">Defining the user tags</a></td>
+</tr>
+<tr>
+<td width="100"><tt>10.&nbsp;3</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Activating tags">Activating tags</a></td>
 </tr>
 <tr>
 <td width="100"><tt>11</tt></td>
-<td><a href="#Selecting a specific configuration">Selecting a specific configuration</a></td>
+<td><a href="#Working on a package">Working on a package</a></td>
 </tr>
 <tr>
 <td width="100"><tt>11.&nbsp;1</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Describing a configuration">Describing a configuration</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Working on a library">Working on a library</a></td>
 </tr>
 <tr>
 <td width="100"><tt>11.&nbsp;2</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Defining the user tags">Defining the user tags</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Working on an application">Working on an application</a></td>
 </tr>
 <tr>
 <td width="100"><tt>11.&nbsp;3</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Activating tags">Activating tags</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Working on a test or external application">Working on a test or external application</a></td>
 </tr>
 <tr>
 <td width="100"><tt>12</tt></td>
-<td><a href="#Working on a package">Working on a package</a></td>
+<td><a href="#Defining a document generator">Defining a document generator</a></td>
 </tr>
 <tr>
 <td width="100"><tt>12.&nbsp;1</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Working on a library">Working on a library</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#An example : the tex document-style">An example : the tex document-style</a></td>
 </tr>
 <tr>
 <td width="100"><tt>12.&nbsp;2</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Working on an application">Working on an application</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#How to create and install a new document style">How to create and install a new document style</a></td>
 </tr>
 <tr>
 <td width="100"><tt>12.&nbsp;3</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Working on a test or external application">Working on a test or external application</a></td>
-</tr>
-<tr>
-<td width="100"><tt>12.&nbsp;4</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Construction of a global environment">Construction of a global environment</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Examples">Examples</a></td>
 </tr>
 <tr>
 <td width="100"><tt>13</tt></td>
-<td><a href="#Defining a document generator">Defining a document generator</a></td>
+<td><a href="#The tools provided by CMT">The tools provided by CMT</a></td>
 </tr>
 <tr>
 <td width="100"><tt>13.&nbsp;1</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#An example : the tex document-style">An example : the tex document-style</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The requirements file">The requirements file</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;1.&nbsp;1</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The general requirements syntax">The general requirements syntax</a></td>
 </tr>
 <tr>
 <td width="100"><tt>13.&nbsp;2</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#How to create and install a new document style">How to create and install a new document style</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The concepts handled in the requirements file">The concepts handled in the requirements file</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.&nbsp;1</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The package structuring style ">The package structuring style </a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.&nbsp;2</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Meta-information : author, manager">Meta-information : author, manager</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.&nbsp;3</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#package, version">package, version</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.&nbsp;4</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Constituents : application, library, document">Constituents : application, library, document</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.&nbsp;5</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Groups">Groups</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.&nbsp;6</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Languages">Languages</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.&nbsp;7</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Symbols">Symbols</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.&nbsp;7.&nbsp;1</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#actions">actions</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.&nbsp;8</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#use">use</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.&nbsp;9</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#patterns">patterns</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.&nbsp;9.&nbsp;1</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Applying a pattern">Applying a pattern</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.10</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmtpath_patterns">cmtpath_patterns</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.11</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#branches">branches</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.12</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Strategy specifications">Strategy specifications</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.13</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#setup_script, cleanup_script">setup_script, cleanup_script</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.14</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#include_path">include_path</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.15</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#include_dirs">include_dirs</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.16</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#make_fragment">make_fragment</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.17</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#public, private">public, private</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.17.&nbsp;1</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Scoping sections">Scoping sections</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;2.18</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#tag, apply_tag">tag, apply_tag</a></td>
 </tr>
 <tr>
 <td width="100"><tt>13.&nbsp;3</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Examples">Examples</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The general cmt user interface">The general cmt user interface</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.&nbsp;1</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt broadcast">cmt broadcast</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.&nbsp;1.&nbsp;1</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Specifying the shell command">Specifying the shell command</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.&nbsp;1.&nbsp;2</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Templates in the shell command">Templates in the shell command</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.&nbsp;2</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt build &lt;option&gt;">cmt build &lt;option&gt;</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.&nbsp;3</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt check configuration">cmt check configuration</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.&nbsp;4</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt check files &lt;reference-file&gt; &lt;new-file&gt;">cmt check files &lt;reference-file&gt; &lt;new-file&gt;</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.&nbsp;5</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt checkout ...">cmt checkout ...</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.&nbsp;6</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt co ...">cmt co ...</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.&nbsp;7</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt cleanup [-csh|-sh]">cmt cleanup [-csh|-sh]</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.&nbsp;8</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt config">cmt config</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.&nbsp;9</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt create &lt;package&gt; &lt;version&gt; [&lt;area&gt;]">cmt create &lt;package&gt; &lt;version&gt; [&lt;area&gt;]</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.10</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt expand model [-strict] &lt;model-string&gt;">cmt expand model [-strict] &lt;model-string&gt;</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.11</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt filter &lt;in-file&gt; &lt;out-file&gt;">cmt filter &lt;in-file&gt; &lt;out-file&gt;</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.12</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt help | --help">cmt help | --help</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.13</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt lock [ &lt;package&gt; &lt;version&gt; [&lt;area&gt;] ]">cmt lock [ &lt;package&gt; &lt;version&gt; [&lt;area&gt;] ]</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.14</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt remove &lt;package&gt; &lt;version&gt; [&lt;area&gt;]">cmt remove &lt;package&gt; &lt;version&gt; [&lt;area&gt;]</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.15</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt remove library_links">cmt remove library_links</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.16</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt run [shell-command]">cmt run [shell-command]</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.17</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt set version &lt;version&gt;">cmt set version &lt;version&gt;</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.18</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt set versions">cmt set versions</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.19</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt setup [-csh|-sh|-bat]">cmt setup [-csh|-sh|-bat]</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.20</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt show &lt;option&gt;">cmt show &lt;option&gt;</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.21</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt system">cmt system</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.22</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt unlock [ &lt;package&gt; &lt;version&gt; [&lt;area&gt;] ]">cmt unlock [ &lt;package&gt; &lt;version&gt; [&lt;area&gt;] ]</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.23</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt version | --version">cmt version | --version</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.24</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt cvstags &lt;module&gt;">cmt cvstags &lt;module&gt;</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.25</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt cvsbranches &lt;module&gt;">cmt cvsbranches &lt;module&gt;</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;3.26</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt cvssubpackages &lt;module&gt;">cmt cvssubpackages &lt;module&gt;</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;4</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The setup and cleanup scripts">The setup and cleanup scripts</a></td>
+</tr>
+<tr>
+<td width="100"><tt>13.&nbsp;5</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt build prototype">cmt build prototype</a></td>
 </tr>
 <tr>
 <td width="100"><tt>14</tt></td>
-<td><a href="#The tools provided by CMT">The tools provided by CMT</a></td>
+<td><a href="#Using cvs together with CMT">Using cvs together with CMT</a></td>
 </tr>
 <tr>
 <td width="100"><tt>14.&nbsp;1</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The requirements file">The requirements file</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;1.&nbsp;1</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The general requirements syntax">The general requirements syntax</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Importing a package into a cvs repository">Importing a package into a cvs repository</a></td>
 </tr>
 <tr>
 <td width="100"><tt>14.&nbsp;2</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The concepts handled in the requirements file">The concepts handled in the requirements file</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.&nbsp;1</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The package structuring style ">The package structuring style </a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.&nbsp;2</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Meta-information : author, manager">Meta-information : author, manager</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.&nbsp;3</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#package, version">package, version</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.&nbsp;4</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Constituents : application, library, document">Constituents : application, library, document</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.&nbsp;5</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Groups">Groups</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.&nbsp;6</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Languages">Languages</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.&nbsp;7</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Symbols">Symbols</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.&nbsp;7.&nbsp;1</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#actions">actions</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.&nbsp;8</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#use">use</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.&nbsp;9</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#patterns">patterns</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.&nbsp;9.&nbsp;1</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Applying a pattern">Applying a pattern</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.10</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmtpath_patterns">cmtpath_patterns</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.11</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#branches">branches</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.12</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Strategy specifications">Strategy specifications</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.13</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#setup_script, cleanup_script">setup_script, cleanup_script</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.14</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#include_path">include_path</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.15</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#include_dirs">include_dirs</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.16</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#make_fragment">make_fragment</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.17</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#public, private">public, private</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.17.&nbsp;1</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Scoping sections">Scoping sections</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;2.18</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#tag, apply_tag">tag, apply_tag</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Checking a package out from a cvs repository">Checking a package out from a cvs repository</a></td>
 </tr>
 <tr>
 <td width="100"><tt>14.&nbsp;3</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The general cmt user interface">The general cmt user interface</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.&nbsp;1</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt broadcast">cmt broadcast</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.&nbsp;1.&nbsp;1</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Specifying the shell command">Specifying the shell command</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.&nbsp;1.&nbsp;2</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Templates in the shell command">Templates in the shell command</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.&nbsp;2</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt build &lt;option&gt;">cmt build &lt;option&gt;</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.&nbsp;3</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt check configuration">cmt check configuration</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.&nbsp;4</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt check files &lt;reference-file&gt; &lt;new-file&gt;">cmt check files &lt;reference-file&gt; &lt;new-file&gt;</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.&nbsp;5</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt checkout ...">cmt checkout ...</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.&nbsp;6</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt co ...">cmt co ...</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.&nbsp;7</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt cleanup [-csh|-sh]">cmt cleanup [-csh|-sh]</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.&nbsp;8</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt config">cmt config</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.&nbsp;9</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt create &lt;package&gt; &lt;version&gt; [&lt;area&gt;]">cmt create &lt;package&gt; &lt;version&gt; [&lt;area&gt;]</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.10</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt expand model [-strict] &lt;model-string&gt;">cmt expand model [-strict] &lt;model-string&gt;</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.11</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt filter &lt;in-file&gt; &lt;out-file&gt;">cmt filter &lt;in-file&gt; &lt;out-file&gt;</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.12</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt help | --help">cmt help | --help</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.13</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt lock [ &lt;package&gt; &lt;version&gt; [&lt;area&gt;] ]">cmt lock [ &lt;package&gt; &lt;version&gt; [&lt;area&gt;] ]</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.14</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt remove &lt;package&gt; &lt;version&gt; [&lt;area&gt;]">cmt remove &lt;package&gt; &lt;version&gt; [&lt;area&gt;]</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.15</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt remove library_links">cmt remove library_links</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.16</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt run [shell-command]">cmt run [shell-command]</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.17</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt set version &lt;version&gt;">cmt set version &lt;version&gt;</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.18</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt set versions">cmt set versions</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.19</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt setup [-csh|-sh|-bat]">cmt setup [-csh|-sh|-bat]</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.20</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt show &lt;option&gt;">cmt show &lt;option&gt;</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.21</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt system">cmt system</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.22</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt unlock [ &lt;package&gt; &lt;version&gt; [&lt;area&gt;] ]">cmt unlock [ &lt;package&gt; &lt;version&gt; [&lt;area&gt;] ]</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.23</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt version | --version">cmt version | --version</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.24</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt cvstags &lt;module&gt;">cmt cvstags &lt;module&gt;</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.25</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt cvsbranches &lt;module&gt;">cmt cvsbranches &lt;module&gt;</a></td>
-</tr>
-<tr>
-<td width="100"><tt>14.&nbsp;3.26</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt cvssubpackages &lt;module&gt;">cmt cvssubpackages &lt;module&gt;</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Querying CVS about some important infos">Querying CVS about some important infos</a></td>
 </tr>
 <tr>
 <td width="100"><tt>14.&nbsp;4</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The setup and cleanup scripts">The setup and cleanup scripts</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Working on a package, creating a new release">Working on a package, creating a new release</a></td>
 </tr>
 <tr>
 <td width="100"><tt>14.&nbsp;5</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#cmt build prototype">cmt build prototype</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Getting a particular tagged version out of CVS">Getting a particular tagged version out of CVS</a></td>
 </tr>
 <tr>
 <td width="100"><tt>15</tt></td>
-<td><a href="#Using cvs together with CMT">Using cvs together with CMT</a></td>
-</tr>
-<tr>
-<td width="100"><tt>15.&nbsp;1</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Importing a package into a cvs repository">Importing a package into a cvs repository</a></td>
-</tr>
-<tr>
-<td width="100"><tt>15.&nbsp;2</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Checking a package out from a cvs repository">Checking a package out from a cvs repository</a></td>
-</tr>
-<tr>
-<td width="100"><tt>15.&nbsp;3</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Querying CVS about some important infos">Querying CVS about some important infos</a></td>
-</tr>
-<tr>
-<td width="100"><tt>15.&nbsp;4</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Working on a package, creating a new release">Working on a package, creating a new release</a></td>
-</tr>
-<tr>
-<td width="100"><tt>15.&nbsp;5</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Getting a particular tagged version out of CVS">Getting a particular tagged version out of CVS</a></td>
+<td><a href="#Interfacing an external package with CMT">Interfacing an external package with CMT</a></td>
 </tr>
 <tr>
 <td width="100"><tt>16</tt></td>
-<td><a href="#Interfacing an external package with CMT">Interfacing an external package with CMT</a></td>
+<td><a href="#The installation area mechanism">The installation area mechanism</a></td>
+</tr>
+<tr>
+<td width="100"><tt>16.&nbsp;1</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The default implementation">The default implementation</a></td>
+</tr>
+<tr>
+<td width="100"><tt>16.&nbsp;2</tt></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Tuning the installation area mechanisms">Tuning the installation area mechanisms</a></td>
 </tr>
 <tr>
 <td width="100"><tt>17</tt></td>
-<td><a href="#The installation area mechanism">The installation area mechanism</a></td>
+<td><a href="#Installing CMT for the first time">Installing CMT for the first time</a></td>
 </tr>
 <tr>
 <td width="100"><tt>17.&nbsp;1</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The default implementation">The default implementation</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Installing CMT on your Unix site">Installing CMT on your Unix site</a></td>
 </tr>
 <tr>
 <td width="100"><tt>17.&nbsp;2</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Tuning the installation area mechanisms">Tuning the installation area mechanisms</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Installing CMT on a Windows or Windows NT site">Installing CMT on a Windows or Windows NT site</a></td>
 </tr>
 <tr>
 <td width="100"><tt>18</tt></td>
-<td><a href="#Installing CMT for the first time">Installing CMT for the first time</a></td>
+<td><a href="#Appendices">Appendices</a></td>
 </tr>
 <tr>
 <td width="100"><tt>18.&nbsp;1</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Installing CMT on your Unix site">Installing CMT on your Unix site</a></td>
+<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Copyright">Copyright</a></td>
 </tr>
 <tr>
 <td width="100"><tt>18.&nbsp;2</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Installing CMT on a Windows or Windows NT site">Installing CMT on a Windows or Windows NT site</a></td>
-</tr>
-<tr>
-<td width="100"><tt>19</tt></td>
-<td><a href="#Appendices">Appendices</a></td>
-</tr>
-<tr>
-<td width="100"><tt>19.&nbsp;1</tt></td>
-<td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Copyright">Copyright</a></td>
-</tr>
-<tr>
-<td width="100"><tt>19.&nbsp;2</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Standard make targets predefined in CMT">Standard make targets predefined in CMT</a></td>
 </tr>
 <tr>
-<td width="100"><tt>19.&nbsp;3</tt></td>
+<td width="100"><tt>18.&nbsp;3</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Standard macros predefined in CMT">Standard macros predefined in CMT</a></td>
 </tr>
 <tr>
-<td width="100"><tt>19.&nbsp;3.&nbsp;1</tt></td>
+<td width="100"><tt>18.&nbsp;3.&nbsp;1</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#CMT static macros">CMT static macros</a></td>
 </tr>
 <tr>
-<td width="100"><tt>19.&nbsp;3.&nbsp;2</tt></td>
+<td width="100"><tt>18.&nbsp;3.&nbsp;2</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Structural macros">Structural macros</a></td>
 </tr>
 <tr>
-<td width="100"><tt>19.&nbsp;3.&nbsp;3</tt></td>
+<td width="100"><tt>18.&nbsp;3.&nbsp;3</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Language related macros">Language related macros</a></td>
 </tr>
 <tr>
-<td width="100"><tt>19.&nbsp;3.&nbsp;4</tt></td>
+<td width="100"><tt>18.&nbsp;3.&nbsp;4</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Package customizing macros">Package customizing macros</a></td>
 </tr>
 <tr>
-<td width="100"><tt>19.&nbsp;3.&nbsp;5</tt></td>
+<td width="100"><tt>18.&nbsp;3.&nbsp;5</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Constituent specific customizing macros">Constituent specific customizing macros</a></td>
 </tr>
 <tr>
-<td width="100"><tt>19.&nbsp;3.&nbsp;6</tt></td>
+<td width="100"><tt>18.&nbsp;3.&nbsp;6</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Source specific customizing macros">Source specific customizing macros</a></td>
 </tr>
 <tr>
-<td width="100"><tt>19.&nbsp;3.&nbsp;7</tt></td>
+<td width="100"><tt>18.&nbsp;3.&nbsp;7</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Generated macros">Generated macros</a></td>
 </tr>
 <tr>
-<td width="100"><tt>19.&nbsp;3.&nbsp;8</tt></td>
+<td width="100"><tt>18.&nbsp;3.&nbsp;8</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Macros related with the installation area mechanisms">Macros related with the installation area mechanisms</a></td>
 </tr>
 <tr>
-<td width="100"><tt>19.&nbsp;3.&nbsp;9</tt></td>
+<td width="100"><tt>18.&nbsp;3.&nbsp;9</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Utility macros">Utility macros</a></td>
 </tr>
 <tr>
-<td width="100"><tt>19.&nbsp;4</tt></td>
+<td width="100"><tt>18.&nbsp;4</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Standard tags generated by CMT">Standard tags generated by CMT</a></td>
 </tr>
 <tr>
-<td width="100"><tt>19.&nbsp;5</tt></td>
+<td width="100"><tt>18.&nbsp;5</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Standard templates for makefile fragments">Standard templates for makefile fragments</a></td>
 </tr>
 <tr>
-<td width="100"><tt>19.&nbsp;6</tt></td>
+<td width="100"><tt>18.&nbsp;6</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#Makefile generation sequences">Makefile generation sequences</a></td>
 </tr>
 <tr>
-<td width="100"><tt>19.&nbsp;7</tt></td>
+<td width="100"><tt>18.&nbsp;7</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The complete requirements syntax">The complete requirements syntax</a></td>
 </tr>
 <tr>
-<td width="100"><tt>19.&nbsp;8</tt></td>
+<td width="100"><tt>18.&nbsp;8</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The default strategies defined in CMT">The default strategies defined in CMT</a></td>
 </tr>
 <tr>
-<td width="100"><tt>19.&nbsp;9</tt></td>
+<td width="100"><tt>18.&nbsp;9</tt></td>
 <td>&nbsp;&nbsp;&nbsp;&nbsp;<a href="#The internal mechanism of cmt cvs operations">The internal mechanism of cmt cvs operations</a></td>
 </tr>
