Changes between Version 51 and Version 52 of VincentFAQ

Timestamp:

May 9, 2005, 5:05:29 PM (19 years ago)

Author:

garonne

Comment:

--

VincentFAQ

@@ -99 +99 @@
 == CMT's design ==
 
-=== What are the architecture of the environment? ===
-This environment is based on the fact that one of its packages (named CMT ) provides the basic
-management tools. CMT , as a package, has very little specificities and as such itself obeys the
-general conventions.
-Then the complete software base is organized in terms of projects (or sub-projects ), containing
-consistently managed package sets. Projects are localized either globally or individually:
-globally using the environment variable CMTPROJECTPATH that describes all locations
-where CMT projects can be found individually using the environment variable CMTPATH that describe all package areas where packages can be found Packages are localized respectively to the projects they belong to.
-It should be noted that the choice of a location for installing CMT itself is totally independent of
-the locations where projects are installed and managed.
-
-CMT is operated through one main user interface : the cmt command, which operates the CMT
-conventions and which provides a set of services for :
- * creating a new package. This operation will create or check the local package directory tree and generate several minimal scripts (see the description of the create command),
- * describing or monitoring :
-    * the relationships between the package and other packages
-    * the configuration features either specified in the current package, or imported from related (used ) ones. (symbols, patterns, fragments)
-    * the constituents of the package in terms of libraries, executables, or generated documents.
- * automatically generating the reconstruction scripts (makefiles ) from this description.
- * recursively acting upon the hierarchy of used packages.
-
-Several other utilities are also provided for some specific activities (such as the automatic
-production of shared libraries, C prototypes, management of interactions between CVS and CMT
-itself, the management of a similar architecture for Windows or OS9 , setting up protections for
-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 :
@@ -166 +139 @@
 complexity of this organization.
 
+=== What are the architecture of the environment? ===
+This environment is based on the fact that one of its packages (named CMT ) provides the basic
+management tools. CMT , as a package, has very little specificities and as such itself obeys the
+general conventions.
+Then the complete software base is organized in terms of projects (or sub-projects ), containing
+consistently managed package sets. Projects are localized either globally or individually:
+globally using the environment variable CMTPROJECTPATH that describes all locations
+where CMT projects can be found individually using the environment variable CMTPATH that describe all package areas where packages can be found Packages are localized respectively to the projects they belong to.
+It should be noted that the choice of a location for installing CMT itself is totally independent of
+the locations where projects are installed and managed.
+
+CMT is operated through one main user interface : the cmt command, which operates the CMT
+conventions and which provides a set of services for :
+ * creating a new package. This operation will create or check the local package directory tree and generate several minimal scripts (see the description of the create command),
+ * describing or monitoring :
+    * the relationships between the package and other packages
+    * the configuration features either specified in the current package, or imported from related (used ) ones. (symbols, patterns, fragments)
+    * the constituents of the package in terms of libraries, executables, or generated documents.
+ * automatically generating the reconstruction scripts (makefiles ) from this description.
+ * recursively acting upon the hierarchy of used packages.
+
+Several other utilities are also provided for some specific activities (such as the automatic
+production of shared libraries, C prototypes, management of interactions between CVS and CMT
+itself, the management of a similar architecture for Windows or OS9 , setting up protections for
+packages (through locks) etc...).
+
+
+
 
 == User FAQ ==