Changes between Version 9 and Version 10 of Doc/SCDB/Usage


Ignore:
Timestamp:
Mar 2, 2007, 4:31:55 PM (17 years ago)
Author:
/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Doc/SCDB/Usage

    v9 v10  
    2222== Checking Compilation Results ==
    2323
    24 When doing changes in configuration, this is often useful to check the resulting profiles before deploying. There is a small tool to help doing that, [source:SCDB/trunk/src/utils/profiles/compare_xml src/utils/profiles/compare_xml]. This tool is part of [source:SCDB SCDB base].
     24When doing changes in configuration, this is often useful to check the resulting profiles before deploying. There is a small tool to help doing that, [source:SCDB/trunk/trunk/src/utils/profiles/compare_xml src/utils/profiles/compare_xml]. This tool is part of [source:SCDB/trunk SCDB base].
    2525
    2626To use this tool, before compiling your changes, you need to copy your current (or reference) `build` directory to something else, by example `build.saved` (default name used by the script). After the compilation, if you run the script without arguments, it will display the list of all profiles that have changed. You can inspect the changes (require a bit of knowledge of profile contents) using option `-v`. Or you can restrict the check to one specific profile with option `-p`. By example :