Changes between Version 16 and Version 17 of Doc/SCDB/Usage


Ignore:
Timestamp:
Sep 29, 2008, 7:51:44 PM (16 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin
Comment:

Add reference to checkdeps.py

Legend:

Unmodified
Added
Removed
Modified

  • Doc/SCDB/Usage

    v16 v17  
    9191
    9292
    93 == Checking Compilation Results ==
     93== Checking Compilation Results and Profile Consistency ==
     94
     95=== Displaying Resulting Changes in Profile ===
    9496
    9597When 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/trunk SCDB base].
    … …  
    124126Another option available, `-d`, extends the comparaison to profile dependencies. This is generally not useful but can be used to do a regression test with a new version of the compiler, for example.
    125127
     128=== Checking Package Dependencies ===
     129
     130Profile compilation cannot check if all the dependencies for all packages present in the profile can be satisfied. By default, this is checked by SPMA on the client before trying to deploy de RPM changes. A tool can be used to check dependencies after compilation but before deployment. This is done by analyzing the profile and checking the metadata for each RPM present, using YUM as a source for the dependency metadata. The took is [source:src/utils/profiles/checkdeps.py src/utils/profiles/checkdeps.py]. Its usage is described in a [wiki:Development/Templates/ClientSideDepsCheck dedicated page].