1 | <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> |
---|
2 | <html> |
---|
3 | <head> |
---|
4 | <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> |
---|
5 | <meta name="GENERATOR" content="Mozilla/4.5 [en] (X11; I; OSF1 V4.0 alpha) [Netscape]"> |
---|
6 | <title>CMT</title> |
---|
7 | </head> |
---|
8 | <body BGCOLOR="#FFFFFF" link="#550088" alink="#007777" alink="#007777"> |
---|
9 | <FONT FACE="Arial, Helvetica" COLOR="#000000"> |
---|
10 | |
---|
11 | <center> |
---|
12 | <h1>CMT</h1> |
---|
13 | </center> |
---|
14 | |
---|
15 | <blockquote> |
---|
16 | <b> |
---|
17 | This <i>configuration management</i> environment, based on some |
---|
18 | management conventions and comprising several shell-based |
---|
19 | utilities, is an attempt to formalize software production and |
---|
20 | especially configuration management around a |
---|
21 | <i>package</i>-oriented principle. |
---|
22 | |
---|
23 | <p>The notion of <i>packages</i> represents hereafter a set of |
---|
24 | software components (that may be applications, libraries, tools |
---|
25 | etc...) that are to be used for producing a <i>system</i> or a |
---|
26 | <i>framework</i>. In such an environment, several persons are |
---|
27 | assumed to participate in the development and the components |
---|
28 | themselves are either independent or related to each other. |
---|
29 | |
---|
30 | <p>The environment provides conventions (for <i>naming</i> |
---|
31 | packages, files, directories and for <i>addressing</i> them) and |
---|
32 | tools for <i>automating</i> as much as possible the |
---|
33 | implementation of these conventions. It permits to |
---|
34 | <i>describe</i> the configuration requirements and automatically |
---|
35 | deduce from the description the effective set of configuration |
---|
36 | parameters needed to operate the packages (typically for |
---|
37 | <i>building</i> them or <i>using</i> them). |
---|
38 | </b> |
---|
39 | </blockquote> |
---|
40 | |
---|
41 | <hr> |
---|
42 | <h2> Project management</h2> |
---|
43 | |
---|
44 | <blockquote> |
---|
45 | CMT is an academic project aimed at providing support to the |
---|
46 | software developments in the context of large physics |
---|
47 | experiments. It is supported by the <a |
---|
48 | href="http://www.lal.in2p3.fr">LAL</a> (Laboratoire de |
---|
49 | l'Accélérateur Linéaire - CNRS), where a |
---|
50 | support team has been setup: |
---|
51 | |
---|
52 | <p> |
---|
53 | <center><i> |
---|
54 | Christian Arnault |
---|
55 | <br>Bruno Mansoux |
---|
56 | <br>Antoine Pérus |
---|
57 | </i></center> |
---|
58 | |
---|
59 | <p>This project is managed in an OpenSource-like style, with |
---|
60 | available sources, and is opened to any contribution from |
---|
61 | anybody. Although it is currently used by Physics experiments, it |
---|
62 | is strongly required to stay experiment neutral, and this |
---|
63 | requirements is fully endorsed in its internal design (eg by |
---|
64 | ensuring that all possible customizations can always be performed |
---|
65 | without modifications to the kernel). |
---|
66 | |
---|
67 | <p>This kind of requirements also implies that portability or |
---|
68 | modularity issues (including environment independance) are |
---|
69 | assigned a quite high priority. |
---|
70 | |
---|
71 | </blockquote> |
---|
72 | |
---|
73 | <hr> |
---|
74 | <h2> Available documentation</h2> |
---|
75 | |
---|
76 | <blockquote> |
---|
77 | <table rows=4> |
---|
78 | <tr> |
---|
79 | <td><center><i>document (html)</i></center></td> |
---|
80 | <td><center><i>ps</i></center></td> |
---|
81 | <td><center><i>pdf</i></center></td> |
---|
82 | <td><center><i>ppt</i></center></td> |
---|
83 | </tr> |
---|
84 | |
---|
85 | <tr> |
---|
86 | <td><a href="CMTDoc.html">CMT manual</a></td> |
---|
87 | <td><a href="CMTDoc.ps.Z"><center>x</center></a></td> |
---|
88 | <td><a href="CMTDoc.pdf"><center>x</center></a></td> |
---|
89 | <td></td> |
---|
90 | </tr> |
---|
91 | <tr> |
---|
92 | <td><a href="CMTFAQ.html">CMT FAQ</a></td> |
---|
93 | <td><a href="CMTFAQ.ps.Z"><center>x</center></a></td> |
---|
94 | <td><a href="CMTFAQ.pdf"><center>x</center></a></td> |
---|
95 | <td></td> |
---|
96 | </tr> |
---|
97 | <tr> |
---|
98 | <td><a href="Doxygen/html/index.html">Doxygen manual</a></td> |
---|
99 | <td></td> |
---|
100 | <td></td> |
---|
101 | <td></td> |
---|
102 | </tr> |
---|
103 | <tr> |
---|
104 | <td><a href="show/index.htm">CMT slides</a></td> |
---|
105 | <td><a href="show.ps.Z"><center>x</center></a></td> |
---|
106 | <td></td> |
---|
107 | <td></td> |
---|
108 | </tr> |
---|
109 | <tr> |
---|
110 | <td><a href="chep-cmt/index.htm">CMT slides presented at CHEP2000</a></td> |
---|
111 | <td><a href="chep-cmt.ps.Z"><center>x</center></a></td> |
---|
112 | <td></td> |
---|
113 | <td></td> |
---|
114 | </tr> |
---|
115 | <tr> |
---|
116 | <td><a href="slides/cern20000420.htm">Slides on the development model</a></td> |
---|
117 | <td><a href="slides/cern20000420.ps"><center>x</center></a></td> |
---|
118 | <td></td> |
---|
119 | <td><a href="slides/cern20000420.ppt"><center>x</center></a></td> |
---|
120 | </tr> |
---|
121 | <tr> |
---|
122 | <td><a href="slides/cern20001129.htm">A CMT tutorial</a></td> |
---|
123 | <td><a href="slides/cern20001129.ps"><center>x</center></a></td> |
---|
124 | <td></td> |
---|
125 | <td><a href="slides/cern20001129.ppt"><center>x</center></a></td> |
---|
126 | </tr> |
---|
127 | <tr> |
---|
128 | <td><a href="slides/cern20010228-2.htm">Another CMT tutorial</a></td> |
---|
129 | <td><a href="slides/cern20010228-2.ps"><center>x</center></a></td> |
---|
130 | <td></td> |
---|
131 | <td><a href="slides/cern20010228-2.ppt"><center>x</center></a></td> |
---|
132 | </tr> |
---|
133 | </table> |
---|
134 | </blockquote> |
---|
135 | |
---|
136 | <hr> |
---|
137 | <h2> The open discussion on CMT</h2> |
---|
138 | |
---|
139 | <blockquote> |
---|
140 | A <a href="http://ccmail.in2p3.fr/archives/cmt-l.html">mailing |
---|
141 | list</a> is setup for managing an open discussion on CMT, |
---|
142 | receiving requests, comments suggestions, bug reports, etc... |
---|
143 | |
---|
144 | <p> You're welcome to subscribe to this list <a |
---|
145 | href="http://ccmail.in2p3.fr/cgi-bin/wa?SUBED1=cmt-l&A=1">here</a> |
---|
146 | or by sending a message with topic "<tt>subscribe CMT-L <your name></tt>" |
---|
147 | to <a |
---|
148 | href="mailto:LISTSERV@IN2P3.FR"><tt>LISTSERV@IN2P3.FR</tt></a>. |
---|
149 | </blockquote> |
---|
150 | |
---|
151 | <hr> |
---|
152 | <h2> The Web access to the main CVS repository of CMT</h2> |
---|
153 | |
---|
154 | <blockquote> |
---|
155 | The CVS repository for CMT is now accessible through CVSWeb <a href="http://www.lal.in2p3.fr/cgi-bin/cvsweb/cvsweb.cgi/CMT/">here</a> !! |
---|
156 | </blockquote> |
---|
157 | |
---|
158 | <hr> |
---|
159 | <h2> Dowloading CMT</h2> |
---|
160 | |
---|
161 | <blockquote> |
---|
162 | |
---|
163 | <p> |
---|
164 | The current stable main version of CMT is v1r10. However |
---|
165 | patched versions can be also produced (fixing bugs or |
---|
166 | providing backward compatible improvements). Users are welcome |
---|
167 | to try these new versions when they appear (and report from |
---|
168 | their experience), although they must be considered as less |
---|
169 | stable than the main current version. |
---|
170 | |
---|
171 | <p> |
---|
172 | Please notice that (at least from v1r6) the odd version |
---|
173 | numbers must be considered as <i>development</i> or |
---|
174 | <i>patched</i> versions (and as such are somewhat unstable), |
---|
175 | and they may be updated from time to time. Whenever such a |
---|
176 | development version comes to the point it can be stabilized, |
---|
177 | it will be renamed to the next even number. As soon as a new |
---|
178 | frozen version is installed, the intermediate patches are |
---|
179 | removed, and new development versions may be proposed |
---|
180 | (eg. under the name <tt>v1r<n+1>p<date></tt>). |
---|
181 | |
---|
182 | <p> |
---|
183 | For each of the following tags, you'll find a distribution kit |
---|
184 | for the sources and (for the latest ones) some prepared binary |
---|
185 | files. |
---|
186 | |
---|
187 | <ul> |
---|
188 | <li> <a href="v1r10p20011126/CMTDownload.html">v1r10p20011126</a> <i>(patched version of v1r10)</i> |
---|
189 | <li> <a href="v1r10p20011113/CMTDownload.html">v1r10p20011113</a> <i>(patched version of v1r10)</i> |
---|
190 | <li> <a href="v1r10/CMTDownload.html">v1r10</a> |
---|
191 | <li> <a href="v1r8p20010710/CMTDownload.html">v1r8p20010710</a> <i>(bug fixed with respect to v1r8 should be fetched instead of v1r8!!)</i> |
---|
192 | <li> <a href="v1r8/CMTDownload.html">v1r8</a> |
---|
193 | <li> <a href="v1r6/CMTDownload.html">v1r6</a> |
---|
194 | <li> <a href="v1r5/CMTDownload.html">v1r5</a> |
---|
195 | <li> <a href="v1r4/CMTDownload.html">v1r4</a> |
---|
196 | </ul> |
---|
197 | |
---|
198 | <p>In order to download the distribution kit, select a root |
---|
199 | directory where CMT will be installed. Create there a directory |
---|
200 | named <tt>CMT</tt> and un-tar all the kits you have selected |
---|
201 | below from this directory: |
---|
202 | |
---|
203 | <blockquote> |
---|
204 | <pre> |
---|
205 | > cd <some root> |
---|
206 | > uncompress CMTv1r10.tar.Z |
---|
207 | > tar xvf CMTv1r10.tar |
---|
208 | </pre> |
---|
209 | </blockquote> |
---|
210 | |
---|
211 | <p>If you wish to build CMT on other plateforms, you just need a |
---|
212 | C++ compiler (supporting templates - STL is not needed) and a |
---|
213 | bash-like shell. |
---|
214 | <p> |
---|
215 | </blockquote> |
---|
216 | |
---|
217 | <hr> |
---|
218 | <h2>Installing and using CMT</h2> |
---|
219 | |
---|
220 | <blockquote> |
---|
221 | <p> |
---|
222 | Once the distribution kit is downloaded, and untarred, resulting |
---|
223 | in a directory structure like: |
---|
224 | |
---|
225 | <blockquote> |
---|
226 | <pre> |
---|
227 | <some root>/CMT/v1r10/... |
---|
228 | </pre> |
---|
229 | </blockquote> |
---|
230 | |
---|
231 | you have to perform the installation by running: |
---|
232 | |
---|
233 | <blockquote> |
---|
234 | <pre> |
---|
235 | unix> cd <some root>/CMT/v1r10/mgr |
---|
236 | unix> ./INSTALL |
---|
237 | unix> source setup.[c]sh |
---|
238 | unix> [g]make |
---|
239 | |
---|
240 | or |
---|
241 | |
---|
242 | dos> cd <some root>\CMT\v1r10\mgr |
---|
243 | dos> call INSTALL.bat |
---|
244 | dos> call setup.bat |
---|
245 | dos> nmake /f nmake |
---|
246 | </pre> |
---|
247 | </blockquote> |
---|
248 | |
---|
249 | Then CMT is installed, and anybody may use CMT simply by doing: |
---|
250 | |
---|
251 | <blockquote> |
---|
252 | <pre> |
---|
253 | unix-csh> source <some root>/CMT/v1r10/mgr/setup.csh |
---|
254 | |
---|
255 | or |
---|
256 | |
---|
257 | unix-sh> . <some root>/CMT/v1r10/mgr/setup.sh |
---|
258 | |
---|
259 | or |
---|
260 | |
---|
261 | dos> call <some root>\CMT\v1r10\mgr\setup.bat |
---|
262 | </pre> |
---|
263 | </blockquote> |
---|
264 | </blockquote> |
---|
265 | |
---|
266 | <hr> |
---|
267 | <h2>Installing and using CMT on Windows</h2> |
---|
268 | |
---|
269 | <blockquote> |
---|
270 | <P> |
---|
271 | Some of the global configuration parameters for CMT <i>may</i> |
---|
272 | optionally be installed as Windows registry entries (although |
---|
273 | the environment variables style of definitions is fully |
---|
274 | supported). This can be done using the <tt>install.exe</tt> |
---|
275 | facility available from the download page or using the |
---|
276 | standard RegEdit facility : |
---|
277 | </P> |
---|
278 | |
---|
279 | <UL> |
---|
280 | |
---|
281 | <LI> |
---|
282 | <tt>HKEY_LOCAL_MACHINE/Software/CMT/root</tt> will contain the root |
---|
283 | directory where CMT is installed (eg. "e:"). |
---|
284 | </LI> |
---|
285 | |
---|
286 | <LI> |
---|
287 | <tt>HKEY_LOCAL_MACHINE/Software/CMT/version</tt> will contain the |
---|
288 | current version tag of CMT ("v1r10" for this version). |
---|
289 | </LI> |
---|
290 | |
---|
291 | <LI> |
---|
292 | <tt>HKEY_LOCAL_MACHINE/Software/CMT/path/</tt> may |
---|
293 | optionally contain a set of text values corresponding to the |
---|
294 | different package global access paths (similar to the |
---|
295 | CMTPATH environment variable. |
---|
296 | </LI> |
---|
297 | |
---|
298 | <LI> |
---|
299 | <tt>HKEY_CURRENT_USER/Software/CMT/path/</tt> may contain a |
---|
300 | set of text values corresponding to the different package |
---|
301 | private access paths (complementary to the latter). |
---|
302 | </LI> |
---|
303 | |
---|
304 | </UL> |
---|
305 | |
---|
306 | </blockquote> |
---|
307 | |
---|
308 | <hr> |
---|
309 | <address> |
---|
310 | <a href="mailto:arnault@asc.lal.in2p3.fr">Christian Arnault</a></address> |
---|
311 | |
---|
312 | <br><!-- Created: Thu Jan 14 19:33:42 MET 1999 --><!-- hhmts start -->Last |
---|
313 | modified: Wed Jun 2 17:56:32 MET DST <!-- hhmts end --></ul> |
---|
314 | |
---|
315 | </body> |
---|
316 | </html> |
---|