| | 1 | = Generating Templates for OS and gLite = |
| | 2 | [[TracNav]] |
| | 3 | |
| | 4 | [[TOC(inline)]] |
| | 5 | |
| | 6 | |
| | 7 | == OS Templates == |
| | 8 | |
| | 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 | * `rpmProvides.pl` : generate a file describing features provided by each RPM in OS distribution |
| | 11 | * `rpmRequires.pl` : generate a file describing for each RPM in the distribution the required dependencies. Uses file produced by previous step as input. |
| | 12 | * `comps2pan.xsl` : generate the templates from standard `comps.xml` file provided in OS distribution. Uses file produced by previous step as input. |
| | 13 | |
| | 14 | It is important to use the `namespace` parameter in `comps2pan.xsl` and indicates `rpmlist` as value. |
| | 15 | |
| | 16 | All these tools are in `utils/misc` in Quattor CVS. |
| | 17 | |
| | 18 | |
| | 19 | == gLite Templates == |
| | 20 | |
| | 21 | Templates for pure gLite services are generated from file `.conf.xml` provided in the config RPM associated with each service. This is done by `create_template.pl` tool, `utils/misc` in Quattor CVS. This tool generates 3 templates per service : |
| | 22 | |
| | 23 | |
| | 24 | 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. |
