Context Navigation

Customization

-              v3
+              v4
 Normally, an attempt is made to guess the OS architecture from the CPU model. But this doesn't fit all situations, in particular with processors that can be installed as 32-bit or 64-bit. You can force the architecture you want to use on a specific machine by défining variable `CPU_ARCH` to the architecture name, using standard architecture names used in RPMs (e.g. i386, x86_64...).
+== OS Errata and RPM Updates ==
+QWG templates provide an easy and flexible way to deploy OS errata RPM as provided by Linux distros or site specific updates to OS RPMs. This is based on 2 templates and a few variables.
+There is a distinct template for standard OS RPM errata and for site specific updates to standard OS RPMs. They are :
+ * `rpms/updates.tpl` : site specific updates to standard OS RPMs.
+ * `PKG_OS_ERRATA_TEMPLATE` : a variable whose value is the name of the template containing errata RPMs to install. The default name is `rpms/errata.tpl` (`.tpl` must be ommited in variable value). QWG templates provide a default errata template and update it regularly based on available errata. A site is free to maintain its own list.
+By default, errata RPMs are not deployed. To do it, variable `PKG_DEPLOY_OS_ERRATA` must be defined to `true`.