Changes between Version 30 and Version 31 of Doc/SCDB/Usage

Timestamp:

Jan 20, 2010, 5:59:07 PM (14 years ago)

Author:

/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin

Comment:

--

Doc/SCDB/Usage

@@ -172 +172 @@
 === Checking Package Dependencies ===
 
-Profile 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 tool is `utils/checkdeps/checkdeps.py`. Its usage is described in a [https://sourceforge.net/apps/mediawiki/quattor/index.php?title=Client_dependencies_check dedicated page].
+Profile 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 tool is `utils/checkdeps/checkdeps`. Its usage and requirements are described in a [https://sourceforge.net/apps/mediawiki/quattor/index.php?title=Client_dependencies_check dedicated page].
+
+One nice feature of `checkdeps` is that it can report missing packages are Pan lines to add to the configuration. This is done with option -p. A typical calling sequence for `checkdeps` is:
+{{{
+util/checkdeps/checkdeps [-p] -x build/xml/mynode.xml
+}}}
 
 === Using panc logging ===