Rev | Line | |
---|
[1] | 1 | <center><h1><b>Introduction</b></h1></center> |
---|
| 2 | |
---|
| 3 | <hr> <br> |
---|
| 4 | |
---|
| 5 | CMT is a <i>configuration management</i> environment, based on some |
---|
| 6 | management conventions and comprises several shell-based utilities. It |
---|
| 7 | is an attempt to formalize software production and especially |
---|
| 8 | configuration management around a <i>package</i>-oriented principle. |
---|
| 9 | |
---|
| 10 | <p>The notion of <i>packages</i> represents hereafter a set of |
---|
| 11 | software components (that may be applications, libraries, tools |
---|
| 12 | etc...) that are to be used for producing a <i>system</i> or a |
---|
| 13 | <i>framework</i>. In such an environment, several persons are assumed |
---|
| 14 | to participate in the development and the components themselves are |
---|
| 15 | either independent or related to each other. |
---|
| 16 | |
---|
| 17 | <p>The environment provides conventions (for <i>naming</i> packages, |
---|
| 18 | files, directories and for <i>addressing</i> them) and |
---|
| 19 | tools for <i>automating</i> as much as possible the |
---|
| 20 | implementation of these conventions. It permits to |
---|
| 21 | <i>describe</i> the configuration requirements and automatically |
---|
| 22 | deduce from the description the effective set of configuration |
---|
| 23 | parameters needed to operate the packages (typically for |
---|
| 24 | <i>building</i> them or <i>using</i> them). |
---|
| 25 | <br> |
---|
| 26 | <hr> |
---|
| 27 | |
---|
Note: See
TracBrowser
for help on using the repository browser.