Changeset 304 for CMT/v1r19/doc/CMTDoc.html

Timestamp:

Nov 9, 2006, 11:15:39 AM (18 years ago)

Author:

garonne

Message:

version v1r19

File:

• CMT/v1r19/doc/CMTDoc.html (modified) (39 diffs)

CMT/v1r19/doc/CMTDoc.html

@@ -19 +19 @@
 <h1><center>CMT</center>
 <center>Configuration Management Tool</center></h1>
-<h2><center>Version v1r18p20051101</center>
+<h2><center>Version v1r19</center>
 <center>Christian Arnault</center>
 <center><tt>arnault@lal.in2p3.fr</tt></center></h2>
-<center><i>Document revision date : 2005-10-30</i></center><hr><h2><a href="#index">General index</a></h2>
+<center><i>Document revision date : 2006-11-09</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>
@@ -471 +471 @@
            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>
+           of a project or in the <tt>cmt/project.cmt</tt>
      project file.
       <p>By default a project inherits the strategies of its
@@ -847 +847 @@
     utilities, using for example the shell command: </p>
 <pre>
-csh&gt; source /lal/CMT/v1r18p20051101/mgr/setup.csh
+csh&gt; source /lal/CMT/v1r19/mgr/setup.csh
 
 or 
 
-ksh&gt; . /lal/CMT/v1r18p20051101/mgr/setup.sh
+ksh&gt; . /lal/CMT/v1r19/mgr/setup.sh
 
 or 
 
-dos&gt; call \lal\CMT\v1r18p20051101\mgr\setup.bat</pre>
+dos&gt; call \lal\CMT\v1r19\mgr\setup.bat</pre>
   <p>Obviously, this operation <i>must</i>
    be performed (once)
@@ -897 +897 @@
 <i><font COLOR="#000077" face="courier new, courier">------------------------------------------
 Configuring environment for project Dev
-CMT version v1r18p20051101.
+CMT version v1r19.
 ------------------------------------------
 Installing the cmt directory
@@ -921 +921 @@
 <i><font COLOR="#000077" face="courier new, courier">------------------------------------------
 Configuring environment for package Foo version v1.
-CMT version v1r18p20051101.                              [1]
+CMT version v1r19.                              [1]
 Root set to /home/arnault/Dev.
 System is Linux-i686                                     [2]
@@ -957 +957 @@
 <i><font COLOR="#007700" face="courier new, courier">------------------------------------------
 Configuring environment for package Foo version v1.
-CMT version v1r18p20051101.
+CMT version v1r19.
 Root set to /ProjectB.
 System is Linux-i686
@@ -1052 +1052 @@
 <i><font COLOR="#000077" face="courier new, courier">------------------------------------------
 Removing package Foo version v1.
-CMT version v1r18p20051101.
+CMT version v1r19.
 Root set to /home/arnault/mydev.
 System is Linux-i686
@@ -1062 +1062 @@
 <i><font COLOR="#000077" face="courier new, courier">------------------------------------------
 Removing package Foo version v1.
-CMT version v1r18p20051101.
+CMT version v1r19.
 Root set to /ProjectB.
 System is Linux-i686
@@ -1210 +1210 @@
 </ol>
     The packages are searched assuming that the directory hierarchy
-below the access paths always follow the convention :
+    below the access paths always follow the convention :
   <ol>
     <li> there is a first directory level exactly named according to
@@ -1309 +1309 @@
   <li>policies for external software organisation</li>
 </ul>
-  Then the global policy package will use them
+      Then the global policy package will use them
 </blockquote>
 <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>
@@ -1627 +1627 @@
         <li>The current minor version id of CMT is a valid tag and
                 takes the form <tt>CMTr&lt;n&gt;</tt>
-         (eg. <tt>CMTr18</tt>
+         (eg. <tt>CMTr19</tt>
       )</li>
         <li>The current patch id of CMT is a valid tag and takes the
@@ -1688 +1688 @@
     </a>
     , a specific context is
-       created, which is materialized with a dedicated tag named
+            created, which is materialized with a dedicated tag named
     <tt>target_&lt;action&gt;</tt>
     , very similarly to the target
@@ -1721 +1721 @@
 &gt; cmt show tags
 <i><font COLOR="#000077" face="courier new, courier">CMTv1 (from CMTVERSION)                                                   [1]
-CMTr18 (from CMTVERSION) package CMT implies [CMTr14]                     [1]
+CMTr19 (from CMTVERSION) package CMT implies [CMTr14]                     [1]
 CMTp20040701 (from CMTVERSION)                                            [1]
 Linux (from uname) package CMT implies [Unix]                             [2]
@@ -1874 +1874 @@
 &gt; cmt show tags
 <i><font COLOR="#000077" face="courier new, courier">CMTv1 (from CMTVERSION)
-CMTr18 (from CMTVERSION)
+CMTr19 (from CMTVERSION)
 CMTp0 (from CMTVERSION)
 Linux (from uname)
@@ -1889 +1889 @@
 &gt; cmt show tags
 <i><font COLOR="#000077" face="courier new, courier">CMTv1 (from CMTVERSION)
-CMTr18 (from CMTVERSION)
+CMTr19 (from CMTVERSION)
 CMTp0 (from CMTVERSION)
 Linux (from uname) package Foo implies [foo]
@@ -1906 +1906 @@
 &gt; cmt show tags
 <i><font COLOR="#000077" face="courier new, courier">CMTv1 (from CMTVERSION)
-CMTr18 (from CMTVERSION)
+CMTr19 (from CMTVERSION)
 CMTp0 (from CMTVERSION)
 Linux (from uname)
@@ -1922 +1922 @@
 &gt; cmt show tags
 <i><font COLOR="#000077" face="courier new, courier">CMTv1 (from CMTVERSION)
-CMTr18 (from CMTVERSION)
+CMTr19 (from CMTVERSION)
 CMTp0 (from CMTVERSION)
 Linux (from uname)
@@ -1931 +1931 @@
 &gt; cmt -tag_add=tag1,tag2,tag3 show tags
 <i><font COLOR="#000077" face="courier new, courier">CMTv1 (from CMTVERSION)
-CMTr18 (from CMTVERSION)
+CMTr19 (from CMTVERSION)
 CMTp0 (from CMTVERSION)
 Linux (from uname)
@@ -2120 +2120 @@
         development. Then we create a <tt>FooTest.cxx</tt>
    source, and
-     generate the associated makefile (specifying that it will be an
+        generate the associated makefile (specifying that it will be an
       executable instead of a library) : </p>
 <pre>
@@ -2280 +2280 @@
   <p>The main concept of this framework is that each document to be
       generated or manipulated must be associated with a "document-type"
-      (also sometimes named "document-style"), which corresponds to a
+     (also sometimes named "document-style"), which corresponds to a
       dedicated make fragment of that name. Then, when specified in a
   <tt>document</tt>
@@ -2678 +2678 @@
                       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>
@@ -3003 +3003 @@
       =<tt>variable-value</tt>
        (without
-                        any space characters around the <tt><tt>"="</tt>
+                        any space characters around the<tt><tt>"="</tt>
       </tt>
                     character), such as in the next example:</p>
@@ -4056 +4056 @@
             </td>
               <td width="500">C source files will
-                                      automatically produce a header file containing
-                               a prototype of all global entry points</td>
+                          automatically produce a header file containing
+                                    a prototype of all global entry points</td>
           </tr>
             <tr>
@@ -4206 +4206 @@
                     include search path of <tt>../src</tt>
        will then simply
-                    disappear, and the <tt>include_path</tt>
+            disappear, and the <tt>include_path</tt>
        statement will
-                  become meaningless. When this happens, include search
+                    become meaningless. When this happens, include search
                     paths will always have to be explicitly specified using the
       <tt>include_dirs</tt>
@@ -4570 +4570 @@
    load
    lock [&lt;p&gt; &lt;v&gt; [&lt;path&gt;]] : lock a package
+   relocate                  : generate setup and cleanup scripts (without makefiles)
    remove &lt;package&gt; &lt;version&gt; [&lt;path&gt;] : remove a package version
    remove library_links    : remove symbolic links towards all imported libraries
@@ -4793 +4794 @@
  command, ie all <tt>CMT</tt>
  packages
-        and versions available through the current <tt>CMTPATH</tt>
+            and versions available through the current <tt>CMTPATH</tt>
  list.
   <p>Typical uses of this <i>broadcast</i>
@@ -4967 +4968 @@
        option (which must precede the
                         command) provides exactly the same features but in a
-                        Windows/nmake context. In this case, all generated
+        Windows/nmake context. In this case, all generated
                         makefiles are suffixed by <tt>.nmake</tt>
        instead of
@@ -5010 +5011 @@
        statements found in
                       the source files. However it's also possible to make
-                      plain use of the standard mechanisms provided by some
+               plain use of the standard mechanisms provided by some
                       standard tools like <tt>cpp -M</tt>
       . In this case, it
@@ -5289 +5290 @@
 <pre>
 &gt; cmt expand model "abcd $(CMTVERSION) efgh"
-<i><font COLOR="#000077" face="courier new, courier">abcd v1r18p20051101 efgh</font></i></pre>
+<i><font COLOR="#000077" face="courier new, courier">abcd v1r19 efgh</font></i></pre>
   </li>
     <li><i>Recursively</i>
@@ -5627 +5628 @@
       <tt>action_value &lt;name&gt;</tt>
         <p>This set of commands displays the raw value
-                    assigned to the symbol (macro, set or action)
+                        assigned to the symbol (macro, set or action)
                         specified as the additional argument. It only presents
                         the final result of the assignment operations
@@ -5716 +5717 @@
     <li><tt>projects</tt>
       <p>This command displays the current knowledge of
-                      sub-project definitions and settings. It shows the
+             sub-project definitions and settings. It shows the
                       project names and their location (ie the corresponding
                       item in <tt>CMTPATH</tt>
@@ -5777 +5778 @@
 #
 # Selection :                                    [4]
-use CMT v1r18p20051101 (/afs/cern.ch/sw/contrib)
+use CMT v1r19 (/afs/cern.ch/sw/contrib)
 use ExternalLibs v4r2p0  (/afs/cern.ch/atlas/offline/external/Gaudi/0.12.1.5)    [5]
 use CLHEP v2r1820p0  (/afs/cern.ch/atlas/offline/external/Gaudi/0.12.1.5)
@@ -6353 +6354 @@
   <tt>OPACS</tt>
    package would have just to provide a use 
-          statement like : </p>
+  statement like : </p>
 <pre class="cmt">
 use OPACS v3 </pre>
@@ -6671 +6672 @@
 csh&gt; cd /Packages 
 csh&gt; &lt;get the tar file from the Web&gt; 
-csh&gt; tar xzf CMTv1r18p20051101.tar.gz 
-csh&gt; cd CMT/v1r18p20051101/mgr 
+csh&gt; tar xzf CMTv1r19.tar.gz 
+csh&gt; cd CMT/v1r19/mgr 
 csh&gt; ./INSTALL 
 csh&gt; source setup.csh 
@@ -6708 +6709 @@
      will
                 contain the current version tag of <tt>CMT</tt>
-                (<tt>"v1r18p20051101"</tt>
+                (<tt>"v1r19"</tt>
    for this version). </li>
     <li><tt>HKEY_LOCAL_MACHINE/Software/CMT/path/</tt>
@@ -6730 +6731 @@
 dos&gt; cd Packages 
 dos&gt; &lt;get the tar file from the Web&gt; 
-dos&gt; cd CMT\v1r18p20051101\mgr 
+dos&gt; cd CMT\v1r19\mgr 
 dos&gt; call INSTALL 
 dos&gt; call setup.bat
@@ -6880 +6881 @@
       </td>
       <td>gives the current release number of CMT</td>
-        <td><tt>18</tt>
+        <td><tt>19</tt>
       </td>
     </tr>
@@ -6887 +6888 @@
       </td>
       <td>gives the current complete version tag of CMT</td>
-        <td><tt>v1r18p20051101</tt>
+        <td><tt>v1r19</tt>
       </td>
     </tr>
@@ -10513 +10514 @@
     <tt>cmt_buildcvsinfos2.sh</tt>
     , which simply receives in its
-     argument the module name onto which we need information. This
+          argument the module name onto which we need information. This
           information is obtained by scanning the files into the
           repository, and an answer is built with the following syntax: