1 | <!-- |
---|
2 | //----------------------------------------------------------- |
---|
3 | // Copyright Christian Arnault LAL-Orsay CNRS |
---|
4 | // arnault@lal.in2p3.fr |
---|
5 | // See the complete license in cmt_license.txt "http://www.cecill.info". |
---|
6 | //----------------------------------------------------------- |
---|
7 | --> |
---|
8 | |
---|
9 | <center><h1><b>Introduction</b></h1></center> |
---|
10 | |
---|
11 | <hr> <br> |
---|
12 | |
---|
13 | CMT is a <i>configuration management</i> environment, based on some |
---|
14 | management conventions and comprises several shell-based utilities. It |
---|
15 | is an attempt to formalize software production and especially |
---|
16 | configuration management around a <i>package</i>-oriented principle. |
---|
17 | |
---|
18 | <p>The notion of <i>packages</i> represents hereafter a set of |
---|
19 | software components (that may be applications, libraries, tools |
---|
20 | etc...) that are to be used for producing a <i>system</i> or a |
---|
21 | <i>framework</i>. In such an environment, several persons are assumed |
---|
22 | to participate in the development and the components themselves are |
---|
23 | either independent or related to each other. |
---|
24 | |
---|
25 | <p>The environment provides conventions (for <i>naming</i> packages, |
---|
26 | files, directories and for <i>addressing</i> them) and |
---|
27 | tools for <i>automating</i> as much as possible the |
---|
28 | implementation of these conventions. It permits to |
---|
29 | <i>describe</i> the configuration requirements and automatically |
---|
30 | deduce from the description the effective set of configuration |
---|
31 | parameters needed to operate the packages (typically for |
---|
32 | <i>building</i> them or <i>using</i> them). |
---|
33 | |
---|
34 | <p>CMT is provided as an Open-Source product (see the <a |
---|
35 | href="http://www.cecill.info/licences/Licence_CeCILL_V2-en.html">licence agreement</a>)</p> |
---|
36 | |
---|
37 | <br> |
---|
38 | <hr> |
---|
39 | |
---|