Changes between Version 6 and Version 7 of Obsolete/Development/Templates/Generated
- Timestamp:
- Jul 27, 2006, 8:51:07 PM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Obsolete/Development/Templates/Generated
v6 v7 8 8 9 9 OS Templates describing RPM list for each OS feature goup are entirely generated from standard Red Hat (or SL) provided `comps.xml` file. This is a 3 steps process : 10 * [source:SCDB/trunk/src/utils/misc/rpmProvides.pl rpmProvides.pl]: generate a file describing features provided by each RPM in OS distribution 11 * [source:SCDB/trunk/src/utils/misc/rpmRequires.pl rpmRequires.pl] : generate a file describing for each RPM in the distribution the required dependencies. Uses file produced by previous step as input. 12 * [source:SCDB/trunk/src/utils/misc/comps2pan.xsl comps2pan.xsl] : generate the templates from standard `comps.xml` file provided in OS distribution. Uses file produced by previous step as input. 10 * [source:SCDB/trunk/src/utils/misc/rpmProvides.pl src/utils/misc/rpmProvides.pl]: generate a file describing features provided by each RPM in OS distribution 11 * [source:SCDB/trunk/src/utils/misc/rpmRequires.pl src/utils/misc/rpmRequires.pl] : generate a file describing for each RPM in the distribution the required dependencies. Uses file produced by previous step as input. 12 * [source:SCDB/trunk/src/utils/misc/comps2pan.xsl src/utils/misc/comps2pan.xsl] : generate the templates from standard `comps.xml` file provided in OS distribution. Uses file produced by previous step as input. 13 14 All these tools are part of [source:SCDB SCDB base]. 13 15 14 16 It is important to use the `namespace` parameter in `comps2pan.xsl` and indicates `rpmlist` as value. 15 17 16 All these tools are in `utils/misc` in Quattor CVS.18 The reference source for these tools is in `util/misc` in [http://quattor.web.cern.ch/quattor/software.htm Quattor CVS]. 17 19 18 20 … … 24 26 * `defaults.tpl` : defines a sensible default value for each property, according to the content of XML file for the service. 25 27 28 Before using this tool, all the glite*-config*rpm must be installed on the machine where the tool will be run. 29 26 30 All these templates used namespaces and their layout is service oriented. There is one directory per service, containing all the templates for the service. All these directories must be placed in `common/glite` directory of gLite templates. 27 31 … … 31 35 LCG, gLite and OS templates allow to define in a specific template a list of RPMs that must be used in replacement of standard RPMs. That means that RPMs listed in this template are installed only if the standard RPM was part of the configuration. 32 36 33 Generally all update RPMs for one product version are kept in one directory. There is a tool to help producing the associated template with the last version of each RPM in this directory, [source:SCDB/trunk/src/utils/misc/rpmUpdates.pl src/utils/misc/rpmUpdates.pl/rpmUpdates.pl], which is part of the SCDB base. This script accept one argument, the RPM repository directory, and write the template on `stdout` which must be redirected to a file.37 Generally all update RPMs for one product version are kept in one directory. There is a tool to help producing the associated template with the last version of each RPM in this directory, [source:SCDB/trunk/src/utils/misc/rpmUpdates.pl src/utils/misc/rpmUpdates.pl/rpmUpdates.pl], which is part of the [source:SCDB SCDB base]. This script accept one argument, the RPM repository directory, and write the template on `stdout` which must be redirected to a file. 34 38 35 39 == Trusted CAs Template == … … 39 43 * For LCG 2.7 : [source:templates/trunk/grid/lcg-2.7.0/rpmlist/pro_software_lcg2_service_security_accepted_cas.tpl rpmlist/pro_software_lcg2_service_security_accepted_cas.tpl] 40 44 41 This template is generated from the contents of the RPM repository containing CAs RPMS with the tools [source:SCDB/trunk/src/utils/CAs/create_template.tpl src/utils/CAs/create_template.tpl/create_template.tpl] which is part of SCDB base.45 This template is generated from the contents of the RPM repository containing CAs RPMS with the tools [source:SCDB/trunk/src/utils/CAs/create_template.tpl src/utils/CAs/create_template.tpl/create_template.tpl] which is part of [source:SCDB SCDB base].
