source: CMT/v1r18p20060301/doc/ReleaseNotes.html @ 154

Last change on this file since 154 was 154, checked in by garonne, 18 years ago

version v1r18p20060301
  • Property svn:eol-style set to native
File size: 25.0 KB
Line 
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<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
10<html>
11  <head>
12    <title>Release notes</title>
13
14    <style type='text/css'>
15li.bug
16{
17  color:#FF0000;
18}
19li.new
20{
21  color:#0000FF;
22  font-weight:bold;
23}
24li.int
25{
26  color:#00FF00;
27}
28<!--  font-style:italic; -->
29    </style>
30  </head>
31 
32  <body BGCOLOR="#FFFFFF" link="#550088" alink="#007777" alink="#007777">
33    <h1>Release notes</h1>
34
35    <blockquote>
36      <center><i>Notation</i></center>
37      <ul>
38        <li class="new">New features</li>
39        <li class="bug">Bug fixes</li>
40        <li class="int">Internal management</li>
41      </ul>
42    </blockquote>
43
44    <ul>
45
46      <li>
47        <b>v1r18p20060301</b>
48       
49        <li class="new">Better support of the non-version-directory mode in severals cases.</li>
50       
51        <li class="new">Add new warning messages in relation with configuration, CMTPATH and setup checkings
52                         (explicitely called with the --warnings option). We also don't remove path item
53                         anymore when they don't exist.</li>
54       
55        <li class="int">Change the internal system for settings environment variables in a proper way.</li>               
56       
57          <ul>
58
59      </ul> 
60       
61       
62      <li>
63        <b>v1r18p20051101</b>
64
65        <ul>
66
67          <!--
68          <li class="new"></li>
69          <li class="bug"></li>
70          <li class="int"></li>
71          -->
72
73          <li class="new">Add a new standard macro definition
74          <tt>$(q)</tt> to hold a double quote. This is useful to
75          define symbol values that contin doublequotes so as they are
76          not filtered out by CMT. Typical usage is to cope with paths
77          containing spaces on Windows. Various fixes have been done
78          to improve the support of spaces in paths</li>
79
80          <li class="new">The <tt>pacman</tt> source file for CMT now
81          includes a constraint on the version of Pacman.</li>
82
83          <li class="bug">Added a mechanism to filter out bad items in
84          a PATH symbol. This was causing troubles at <tt>source
85          setup</tt> time</li>
86
87          <li class="bug">Added a protection against old protocols in
88          the CVS pluggin</li>
89
90          <li class="bug">Better support of release-less projects on
91          Windows</li>
92
93          <li class="bug">Added a protection against single level
94          directories in CMTPATH</li>
95
96          <li class="bug">Added a protection against unexisting
97          makefile fragments when running the <tt>clean</tt> target.</li>
98
99          <li class="bug">The definition of standard macros was not
100          properly set when using the <tt>cmt broadcast</tt>
101          command. Thus environment variables where badly preset.</li>
102
103          <li class="int">Improve the automatic preparation of CMT releases</li>
104
105          <li class="int">The internal <tt>Makefile</tt> structure has
106          been cleaned up to remove obsolete internal targets (leading
107          to confusing behavours in some cases)</li>
108
109     </ul>
110
111      </li>
112
113      <li>
114        <b>v1r18p20050901</b>
115
116        <ul>
117
118          <!--
119          <li class="new"></li>
120          <li class="bug"></li>
121          <li class="int"></li>
122          -->
123
124          <li class="new">Package creation (either from the <tt>cmt
125          create</tt> or the <tt>cmt co</tt> commands is affected by
126          the specification of the structuring style or of the
127          structuring strategy.</li>
128
129          <li class="new">Introduce a new strategy structure_strategy
130          with only one value with/out_version_directory. This is
131          mostly useful when installed in a project file to condition
132          the behaviour of package creation afterwards</li>
133
134          <li class="new">Support dependency building using external
135          tools such as cpp -M. Fix the cmt_build_des.sh wrapper
136          script to properly format the command output.</li>
137
138          <li class="new">Perform the cmt checkout onto a project even
139          if the basic directory structure of the project is already
140          in place.</li>
141
142          <li class="new">When no current project is defined the
143          strategies are taken from the top project (eg obtained from
144          the CMTPATH)</li>
145
146          <li class="new">The include_dirs statement can now be hidden
147          in a private section.</li>
148
149          <li class="new">The include_dirs statement now accepts a
150          macro reference as its value</li>
151
152
153
154          <li class="bug">Fix incorrect generation of XXXROOT and
155          XXXCONFIG environment variables according to strategies</li>
156
157          <li class="bug">Protect against missing un/install targets</li>
158
159          <li class="bug">Fix a typo in cmt_uninstall_action.bat
160          resulting in bad management of make cleanup on Windows</li>
161
162          <li class="bug">When creating a parent-less project, link it
163          to exisiting top project(s) and upgrade strategies
164          accordingly. Avoid confusions when mixing explicit CMTPATH,
165          CMTPROJECTPATH and project files </li>
166
167          <li class="bug">Don't apply include_dirs when their expanded
168          value is empty (avoid killing -I"")</li>
169
170          <li class="bug">Reset CMTPATH to empty when filling in
171          CMTPATH from projects (avoid confusions and
172          dupplications)</li>
173
174          <li class="bug">Fix a bug in dependency builder that missed
175          some statements after a single line C++ comment</li>
176
177          <li class="bug">Cleanup unneeded duplicate path
178          separators</li>
179
180          <li class="bug">Fix a bug in standard macro generation for
181          projects</li>
182
183        </ul>
184
185      </li>
186
187      <li>
188        <b>v1r18p20050501</b>
189
190        <ul>
191
192          <!--
193          <li class="new"></li>
194          <li class="bug"></li>
195          <li class="int"></li>
196          -->
197
198          <li class="new">Fill in a pacman cache for CMT using pacman3
199          syntax. The Pacman package name is CMT.</li>
200
201          <li class="new">Extend the recursive checkout mechanism to
202          projects. The recursivity covers the use relationships
203          between projects and propagates to packges of a project when
204          the container package is specified in the project file.</li>
205
206          <li class="new">Add the cvssubprojects query command to
207          retrieve subprojects at a CVS repository level</li>
208
209          <li class="new">Add a container statement in project
210          file. The syntax is like use statements. It indicates that a
211          container-like package exists in the project. This is useful
212          for recursive checkout operations.</li>
213
214          <li class="int">Migrate to a new version of the CVS
215          pluggin. Now the protocol level is explicitly referenced
216          when sending CVS requests via the pluggin. The new protocol
217          gives the nature of the CVS module: is it a project or a
218          package. The protocol level is specified in a dedicated
219          macro in the CMT requirements file.</li>
220
221          <li class="bug">Fix the production of shared libraries on CYGWIN</li>
222
223          <li class="bug">Fix ambiguities between physical paths and
224          logical paths in PATH variables management</li>
225
226          <li class="bug">Fix arg counting bugs in cvstags and cvssubpackages commands</li>
227
228        </ul>
229
230      </li>
231
232      <li>
233        <b>v1r18p20050401</b>
234
235        <ul>
236
237          <!--
238          <li class="new"></li>
239          <li class="bug"></li>
240          <li class="int"></li>
241          -->
242
243          <li class="new">Introduce a new bug reporting system: Trac</li>
244
245          <li class="new">Accept HEAD or head as a valid version tag for packages</li>
246
247          <li class="new">The path of CMT is removed from
248          CMTPATH. Packages aside CMT are no longer reachable by
249          default</li>
250
251          <li class="new">Major restructuring of the project
252          management and package localisation. The most important
253          parameter becomes the search path CMTPROJECTPATH for
254          projects. Then CMTPATH is deduced from the effective list of
255          used projects. Project files and the dependency graph
256          described by the project use statement becomes a central
257          mechanism.</li>
258
259          <li class="new">Introduce the management of releases for
260          projects. Release must exactly match</li>
261
262          <li class="new">Install a mechanism to detect unused tags
263          from arguments or CMTSITE. This is performed during the
264          setup generation</li>
265
266          <li class="int">Source code management tansfered to SVN</li>
267
268          <li class="int">Restructure the strategy management to make
269          it fully generic.</li>
270
271          <li class="bug">Fix poor management of unknown commands </li>
272
273          <li class="bug">Suppress the export action for alias in setup.sh</li>
274
275          <li class="bug">Fix a problem in TMPDIR management with
276          multi directory level</li>
277
278          <li class="bug">Fix a problem in cmt show packages</li>
279
280          <li class="bug">Fix bad parsing of various cmt commands</li>
281
282          <li class="bug">Fix an internal bug causing misfunction in
283          the -import parameter of constituents.</li>
284
285          <li class="bug">Fix fragment for action to improve argument transmission</li>
286
287          <li class="bug">Fix pdb files for Visual about debug mode</li>
288
289        </ul>
290
291      </li>
292
293      <li>
294        <b>v1r18p20041201</b>
295
296        <ul>
297
298          <!--
299          <li class="new"></li>
300          <li class="bug"></li>
301          <li class="int"></li>
302          -->
303
304          <li class="int">Suppress the completely unused makefile strategy</li>
305
306          <li class="bug">Really apply the project specific setup
307          strategy to control the generation of ROOT or CONFIG
308          env. variables.</li>
309
310          <li class="new">Change default build strategy to <tt>without_installarea</tt></li>
311
312          <li class="new">${CMTROOT} is no longer an automatic part of
313          the CMTPATH. Nor the current package automatically defines
314          an entry in the CMTPATH search list. However a feature
315          partly compensates this evolution: the current project
316          (i.e. the current package area, where the developer stands)
317          is autmatically detected when its project file exists
318          (i.e. when its cmt/project.cmt file exists). For instance,
319          this suppresses the need to set CMTPATH when working in one
320          single project.</li>
321
322          <li class="new">The general cmt command parsing mechanism
323          has been revisited and now "actions" are considered as
324          extended cmt commands and no longer need the "cmt do
325          &lt;action&gt;" syntax. One can directly use "cmt
326          &lt;action&gt;" when the action does not conflict with
327          internal cmt commands.</li>
328
329          <li class="new">Command line arguments are transmitted to
330          "actions" now through the new standard "cmt_args" macro</li>
331
332          <li class="bug">Really force the settings of all
333          Env. variables before running internal cmmands through
334          broadcast, run or do commands.</li>
335
336          <li class="new">The "cmt run" command transmits all its
337          arguments to the launched action</li>
338
339          <li class="new">Revisit the production of dependency files,
340          to consider the changes made to the configuration in general
341          in addition to the usual source changes. This consists in
342          generating one stamp file per source, touched when its
343          contents change rather than when recomputing the
344          dependencies.</li>
345
346          <li class="bug">Better protections for CMTPATH entries</li>
347
348          <li class="int">Major internal restructuring of the CMT
349          package. Internal sources are now in ../source, ../src only
350          contains publicly exported configuration files, fragments
351          are in ../mgr/fragments. This is for constructing a really
352          autonomous binary kit for CMT (eg for Fink) (without needing
353          to export two kits)</li>
354
355          <li class="bug">Now produce the last revision date of the
356          CMT documentation. Insert the complete version tag rather
357          than just the base version tag.</li>
358
359          <li class="new">Suppress the systematic production of
360          bundles on Darwin machines. This must now be done
361          explicitly.</li>
362
363          <li class="bug">The algorithm for commpressing paths with
364          ../ patterns now takes into account the presence of ${xxx}
365          expressions that cannot be reduced. It also better handle
366          various patterns that used to produce failures.</li>
367
368          <li class="bug">A global checking of the configuration is
369          performed first when running Make</li>
370
371          <li class="new">Incompatible major ids in the version
372          numbers are now managed like the minor id, ie. the decision
373          is taken in a similar way. The usual error message is
374          displayed but this is no longer fatal, and a decision is
375          taken</li>
376
377        </ul>
378
379      </li>
380
381      <li>
382        <b>v1r16p20040901</b>
383
384        <ul>
385
386          <!--
387          <li class="new"></li>
388          <li class="bug"></li>
389          <li class="int"></li>
390          -->
391
392          <li class="new">Introduce the support of SLC3 (Scientific
393          Linux) platforms</li>
394
395          <li class="new">Trigger the reconstruction of the dependency
396          makefile fragment from a change in the
397          &lt;package&gt;_setup.make, ie from any change in tags, uses
398          or CMTPATHs</li>
399
400          <li class="new"><tt>CMTBIN</tt> now follows a new convention
401          on Unix `uname`-`uname -m` to differentiate among Linux
402          platforms.</li>
403
404          <li class="new">Introduce a new -strict option to the cmt
405          expand model to support model files freely formatted. This
406          implied securing the user defined model elements by the
407          <tt>cmts</tt> or <tt>cmtv</tt> name space
408          keywords. <tt>cmts:xxx</tt> indicates a scalar modelling
409          element <tt>xxx</tt> meant to be expanded only
410          once. <tt>cmtv:yyy</tt> indicates a vector modelling element
411          <tt>yyy</tt> meant to be expanded once per item in the
412          vector of values.</li>
413
414          <li class="new">Better management of temporary file
415          generation. Now support the standard TMPDIR environment
416          variable to redirect temporary locations.</li>
417
418          <li class="int">Apply the new GPL-like licence officially
419          provided by CNRS-CEA-INRIA</li>
420
421          <li class="int">Use stderr instead of stdout to display
422          error and warning messages. Mainly to better expose messages in
423          the source setup operations</li>
424
425          <li class="bug">Protect against source files not found (avoid infinite loops in make)</li>
426
427          <li class="bug">Better management of the build strategy on
428          installation area to generate various automatic macros or
429          sets (installarea_linkopts, PATH, LD_LIBRARY_PATH,
430          etc...)</li>
431
432          <li class="bug">Revisit the package scan algorithm to
433          improve the detection of directory structure of packages as
434          well as their version tags.</li>
435
436          <li class="bug">Compress the path definitions (ie compress
437          the ../xxx patterns) and use the compressed paths
438          everywhere</li>
439
440        </ul>
441
442      </li>
443
444      <li>
445        <b>v1r16p20040701</b>
446
447        <ul>
448
449          <!--
450          <li class="new"></li>
451          <li class="bug"></li>
452          <li class="int"></li>
453          -->
454
455          <li class="bug">Better generation of .def files for DATA</li>
456
457          <li class="bug">fix a bug that impacted on the order of
458          compatible use requests with different wilcarded specifications</li>
459
460        </ul>
461
462      </li>
463
464      <li>
465        <b>v1r16p20040527</b>
466
467        <ul>
468
469          <!--
470          <li class="new"></li>
471          <li class="bug"></li>
472          <li class="int"></li>
473          -->
474
475          <li class="new">Generate the <tt>target_${CONSTITUENT}</tt>
476          tag to trigger configuration control per target. This
477          feature is only activated when the new <tt>-target_tag</tt>
478          option is specified to a constituent. Specific tag makefiles
479          are then generated for those targets. This tag is activated
480          either when <tt>make &lt;target&gt;</tt> or <tt>cmt do
481          &lt;action&gt;</tt> is run.</li>
482
483          <li class="new">Add a section on package semantics in the documentation</li>
484
485          <li class="new">The <tt>apply_tag</tt> keyword now accepts macro expansion for its argument.</li>
486
487          <li class="new">Add the support for Enterprise Linux</li>
488
489          <li class="new">Create automatic tags from
490          <tt>cmt_hardware</tt> <tt>cmt_system_version</tt> and
491          <tt>cmt_compiler_version</tt></li>
492
493          <li class="new">Add a filtering script to keep 3 digits instead of 2</li>
494
495          <li class="int">Start the implementation of a centralized log message facility</li>
496
497          <li class="int">Implement a <tt>READONLY</tt> mode to
498          Makefiles to generate all intermediate files in
499          <tt>/tmp/CMT_*</tt> rather than in <tt>../cmt</tt></li>
500
501          <li class="int">Associate a dedicated project with CMTHOME and CMTUSERCONTEXT to manage strategies</li>
502
503          <li class="bug">Set the macro <tt>shlibsuffix</tt> for Win32</li>
504          <li class="bug">Use /bin/pwd instead of the raw pwd in various CMT scripts for Unix</li>
505          <li class="bug">Fix misunderstanding of of version specification of the form v1r2p (ie without a trailing number)</li>
506          <li class="bug">Explicitly close the scope sections at the end of requirements files</li>
507
508        </ul>
509
510      </li>
511
512      <li>
513        <b>v1r16</b>
514
515        <ul>
516
517          <!--
518          <li class="new"></li>
519          <li class="bug"></li>
520          <li class="int"></li>
521          -->
522
523          <li class="new">Offer an [x]emacs mode for editing requirements files</li>
524
525          <li class="new">Permit macro expressions in the <tt>tag</tt> statement</li>
526
527          <li class="new">Possibility to specify additional
528          <tt>mount_filters</tt> in <tt>.cmtrc</tt></li>
529
530          <li class="new">Introduce new regexp-based remove operations
531          for symbols <tt>macro_remove_regexp</tt>,
532          <tt>set_remove_regexp</tt> and
533          <tt>path_remove_regexp</tt></li>
534
535          <li class="new">Add <tt>-n</tt> and <tt>-v</tt> options to
536          <tt>cmt cvs</tt> commands to support simulation and verbose
537          modes</li>
538
539          <li class="new">Ensure that the <tt>constituents</tt> macro is always private</li>
540
541          <li class="new">Introduce support for <i>projects</i>
542          associated with package areas, i.e. one project per item in
543          <tt>CMTPATH</tt>. Possibility to setup strategies per
544          project. Project definitions stored in a new
545          <tt>cmt/project.cmt</tt> top level file. New
546          <tt>&lt;package&gt;_project</tt> standard macro. And
547          associated pattern templates.</li>
548
549          <li class="new">Make <tt>CMTINSTALLAREA</tt> a macro instead of a set</li>
550
551          <li class="new">Suppress dependency computation when the
552          <tt>make QUICK=1</tt> option is used</li>
553
554          <li class="new">New <i>action</i> concept to support
555          simplified shell action definition. Action is an extension
556          of the generic symbol mechanism (like macros), thus defining
557          an action uses the same syntax as macros. Actions are
558          triggered with <tt>make</tt> or <tt>cmt do</tt></li>
559
560          <li class="new"><i>public</i> and <i>private</i> section can be ended by a
561          new keyword <tt>end_public</tt> <tt>end_private</tt>. Ending
562          keywords switch back to the previous scope active before the
563          most recent opening keyword</li>
564
565          <li class="new">Can use a pattern name as a plain CMT
566          keyword. I.e. the <tt>apply_pattern</tt> keyword is optional
567          except to resolve ambiguities</li>
568
569          <li class="int">Generate part of the standard macros before
570          reading the requirements file</li>
571
572          <li class="int">Lots of internal optimisations checked with
573          <tt>valgrind</tt> and <tt>gprof</tt></li>
574
575          <li class="bug">Only set non empty environment variables</li>
576
577          <li class="bug">Fix bad definition of <tt>&lt;PACKAGE&gt;VERSION</tt></li>
578
579          <li class="bug">Add dependency to all stamps file to trigger rebuild of shared libraries</li>
580
581          <li class="bug">Add dependency to all requirements file to trigger rebuild of applications</li>
582
583          <li class="bug">Suppress install area cleanup action from
584          cmt config and cmt setup</li>
585
586          <li class="bug">Improved syntax checking on constituents</li>
587
588          <li class="bug">Fix construction of paths when symlinks
589          exist along pwd</li>
590
591          <li class="bug">Added various protections for bad pattern
592          syntaxes</li>
593
594        </ul>
595
596      </li>
597      <li>
598        <b>v1r14p20031120</b>
599        <ul>
600          <li class="new">Add a new standard macro $(&lt;group&gt;_dependencies)to specify global dependencies for a group</li>
601          <li class="new">Add support for bundles on Darwin platforms</li>
602          <li class="bug">Consider symlinked paths in CMTPATH entries</li>
603          <li class="bug">Always setup cmtpath patterns even if the current installation area is undefined</li>
604
605          <li class="new">Provide a generic pacman manifest file for
606            CMT. All instances of the "&lt;version&gt;" pattern need to be
607            substituted by the effective version of CMT to make it a
608            real pacman file as follows:
609            <pre>sed -e 's#[&lt;]version[&gt;]#'`cmt -quiet version`'#g' $CMTROOT/mgr/CMT.pacman</pre>
610          </li>
611
612        </ul>
613      </li>
614
615      <li>
616        <b>v1r14p20031027</b>
617        <ul>
618          <li class="bug">Fix a bug in the bootstrap mechanism to define CMTINSTALLAREA</li>
619        </ul>
620      </li>
621
622      <li>
623        <b>v1r14p20031022</b>
624        <ul>
625          <li class="new">Add the possibility to specify exclusion files when installing directories in Installation Area (on windows only)</li>
626          <li class="bug">Fix a bug : CMTINSTALLAREA symbol has to be defined before all other symbols in set_standard_macros</li>
627          <li class="bug">Few fixes on nmake flavour of install area mechanisms</li>
628          <li class="new">Generate &lt;package&gt;_cmtpath and &lt;package&gt;_offset also for current package</li>
629          <li class="bug">Fix warning messages that confuse csh when environment variables are not defined</li>
630        </ul>
631      </li>
632
633      <li>
634        <b>v1r14p20031014</b>
635        <ul>
636          <li class="bug">Fix a problem in broadcast operation for handling return status 2 (caused to unexpectedly break the loop in some cases)</li>
637          <li class="bug">Force auto_imports to On when context is unspecified (internal)</li>
638          <li class="bug">Stop trying to make use of PWD</li>
639          <li class="bug">Fix a bug in internal incomplete expansion of macros</li>
640          <li class="bug">Fix a bug in consistency checks of PWD vs CMTINSTALLAREA</li>
641          <li class="new">Convert $(cmtpath) and $(offset) macros to $(package_cmtpath) and $(package_offset)</li>
642          <li class="new">Add dependency list for constituent makefile similar to the constituent target (force the same build order)</li>
643          <li class="bug">Fix a bug in use graph internal management</li>
644          <li class="bug">Fix setup script calling mechanism in no_version style</li>
645          <li class="new">Add a -k=&lt;regexp&gt; argument for selection patterns of constituent sources.</li>
646          <li class="new">Support wildcarded suffixes (*.*) in constituent sources</li>
647          <li class="new">Standardize the output format of show uses (make it reliable for user scripts)</li>
648        </ul>
649      </li>
650
651      <li>
652        <b>v1r14p20030811</b>
653        <ul>
654          <li class="bug">Trailing slashes on offset specification in use statement were causing troubles. Now they are properly handled.</li>
655          <li class="new">The broadcast pattern as well as the standard macro &lt;cmtpath&gt; is now renamed &lt;package_cmtpath&gt; to avoid confusion with the CMTPATH variable on Windows.</li>
656          <li class="int">Make use of ${PWD} when available to acquire the value for "cmt show pwd"</li>
657          <li class="bug">Add or refresh tuning for CYGWIN and for LynxOS</li>
658          <li class="bug">Work around a limitation of some old version of the C++ compiler on LynxOS</li>
659          <li class="new">Improve the display of incompatible use specifications.</li>
660          <li class="int">Dynamically create the CMTDownload.html web page to really reflect what is available when installing the CMT release on the primary CMT web site.</li>
661          <li class="bug">Setup.bat scripts on DOS are now relocatable wrt heterogeneous file systems (AFS, DFS, etc...)</li>
662        </ul>
663      </li>
664
665      <li>
666        <b>v1r14p20030620</b>
667        <ul>
668          <li class="new">introduce a generic "Unix" tag for all Unix platforms. Both Linux, HP-UX, LynxOS, alpha, ... do validate Unix</li>
669          <li class="new">hide the make_fragments declaration in private sections. This was not true previously. A make_fragment declaration installed in a private section will now be hidden to clients.</li>
670          <li class="bug">convert ${} into $() syntax for tag makefiles on Windows. This actually reverts to a feature of an old CMT version which had disappeared. This was causing a problem since the ${} syntax is not understood by nmake</li>
671          <li class="new">add a command "cmt show use_paths &lt;target&gt;" to display all possible paths to the target package. This is useful to understand how a given package is reached, for instance when it is desired to cut the use relationship and make it private somewhere in the graph.</li>
672          <li class="new">add a command "cmt show cycles" to display circular dependencies in the use graph.</li>
673          <li class="new">provide a binary RPM for CMT itself (only for redhat 7.2 distribution). It is downloadable from the usual Download page and provide a complete installation of CMT (including make fragments, binary, etc..). It is a relocatable RPM (install it using the --relocate option). (See the install WEB page for complete notice)</li>
674          <li class="new">Add an extended script to retrieve information about Linux version (cmt_linux_version.sh). It supports Redhat, Debian, Suse. It is used to compute the cmt_system_version macro (contributions from Clark McGrew and Wim Lavrijsen)</li>
675          <li class="bug">The setup scripts for Windows now use %TEMP% instead of %HOMEDRIVE%%HOMEPATH% to store temporary files (contributions from Pere Mato and Florence Ranjard)</li>
676          <li class="new">Add the --public and --private global options for cmt commands, to control whether the use graph traverses or not the private sections:
677<pre>
678&gt; cmt --public ...
679</pre>
680       only sees public uses (default behavior for most commands but not for cmt broadcast and cmt show uses which traverse the private sub graphs)
681<pre>
682&gt; cmt --private ...
683</pre>   
684       forces the traversal of private subgraphs. This is already the default behavior for cmt show uses and for cmt broadcast, but can now be applied to any CMT command.</li>
685          <li class="bug">A global pattern specifying private sections did not really generate private definitions</li>
686        </ul>
687      </li>
688
689<!--
690      <li>
691        <b></b>
692        <ul>
693          <li class=""></li>
694        </ul>
695      </li>
696-->
697
698    </ul>
699
700
701    <hr>
702    <address><a href="mailto:arnault@lal.in2p3.fr">Christian Arnault</a></address>
703  </body>
704</html>
Note: See TracBrowser for help on using the repository browser.