| 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 : |
| | 9 | To add support for a new OS distribution, the recommended method is to copy with `svn cp` the template hierarchy for the last already supported version with the same architecture. Main part of templates for one specific OS version is RPM lists, with one template per RPM group. This is entirely generated from distribution description. |
| | 10 | |
| | 11 | After generating templates for RPM groups, the following templates must be modified or reviewed : |
| | 12 | * `repository/config.tpl` : edit to point to right RPM repositories ofr the OS version. There is generally one repository per OS version/arch combination. |
| | 13 | * `config/os/kernel_arch_version.tpl` : update the kernel version and variant to match what is provided by the distribution. |
| | 14 | * `config/glite/*/base.tpl` and `config/glite/*/postconfig.tpl` : may require some adjustement for RPMs explicitly added/updated/removed. |
| | 15 | |
| | 16 | === RPM Lists === |
| | 17 | |
| | 18 | 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 done by tool [source:SCDB/trunk/src/utils/misc/buildOSTemplates src/utils/misc/buildOSTemplates]. It requires 2 parameters : |
| | 19 | * Location of OS distribution : this must me the directory containing both a `RPMS` and a `base` directory. |
| | 20 | * Templates location : where to put the generated templates. If this is part of SCDB, the script takes care of adding the necessary files to SVN. |
| | 21 | |
| | 22 | [source:SCDB/trunk/src/utils/misc/buildOSTemplates src/utils/misc/buildOSTemplates] is a wrapper to 3 other tools, hiding the somewhat complex option arguments : |