Changes between Version 49 and Version 50 of VincentFAQ

Timestamp:

May 9, 2005, 4:46:41 PM (21 years ago)

Author:

garonne

Comment:

--

VincentFAQ

@@ -6 +6 @@
 Web site : [http://www.cmtsite.org/ http://www.cmtsite.org/]    [[BR]]
 
-
 {{{
 #!html 
 <BLINK><font color="#FF0000"><u><b>IMPORTANT</b></u></font></BLINK>: This FAQ is not completed and still under construction. Some answers are missing.
 }}}
-
 
 [[TOC(inline)]]
@@ -127 +125 @@
 packages (through locks) etc...).
 
+=== What is the conventional directory tree for projets and packages? ===
+
+This environment relies on a set of conventions, mainly for organizing the directories where
+projects and packages are maintained and developed :
+ * Each package is installed in a standard directory structure defined at least as follows:
+
+{{{
+<some root>/<Package mnemonic>/<version mnemonic>/cmt 
+}}}
+or (obsolescent convention )
+{{{
+<some root>/<Package mnemonic>/<version mnemonic>/mgr
+}}}
+
+The <version mnemonic> directory level may also be omitted, in which case the version
+information will be stored inside the cmt directory in a conventional file named
+version.cmt leading to the following alternate organization:
+<some root>/<Package mnemonic>/cmt/version.cmt
+In both cases, the cmt directory holds the main source of information needed by CMT : the
+requirements file. All CMT -related operations are generally executed from this directory.
+This style of organization should be considered as the basic (and unique) criterion for a
+package to be recognized as a valid CMT package . Any other structuring convention will be
+supported by CMT and its operations can always be customized to follow them
+This structure is a central concept since all relationships between packages relies on the
+package identification which unambiguously and exclusively consists in the duet [
+package-name , package-version ] (or package-name only when the version directory level
+is omitted).
+
+ * Constructing the internal structure of a package.
+
+Many other parallel directory branches (similar to cmt ) such as src , include or test
+may be freely added to this list according to the specific needs of each package. In particular,
+a set of such parallel branches are expected to contain binary outputs (those that compilers,
+linkers, archive managers or other kinds of code or pseudo-code generators can produce).
+Their name always corresponds to the particular configuration tag used to produce the
+output (such as the machine or operating system type). The CMT toolkit provides, through
+the cmt system utility, a default value for this token. An environment variable
+(CMTCONFIG ) is also assigned to this value.
+Each branch may in addition be freely structured, and there is no constraint to the
+complexity of this organization.
+
+
+
 == User FAQ == 
 
@@ -181 +222 @@
   You can write to <a href="mailto:CMT-L@IN2P3.FR"> mailing list </a> or any of the developers.
 }}}
-
-