From 9d3a445882c99a7d5a7aa929dc00abe1b9b20d88 Mon Sep 17 00:00:00 2001 From: Sol Jerome Date: Tue, 17 Apr 2012 13:35:37 -0500 Subject: Packages: Add Essential packages to specification (#1084) Signed-off-by: Sol Jerome --- doc/server/plugins/generators/packages.txt | 23 +++++++++++++++-------- 1 file changed, 15 insertions(+), 8 deletions(-) (limited to 'doc') diff --git a/doc/server/plugins/generators/packages.txt b/doc/server/plugins/generators/packages.txt index e4035053a..2bc3dab31 100644 --- a/doc/server/plugins/generators/packages.txt +++ b/doc/server/plugins/generators/packages.txt @@ -205,14 +205,13 @@ something like this:: .. versionadded:: 1.1.0 - The default behavior of the Packages plugin is to not make - any assumptions about which packages you want to have added - automatically. For that reason, neither **Recommended** nor - **Suggested** packages are added as dependencies by default. You - will notice that the default behavior for apt is to add Recommended - packages as dependencies. You can configure the Packages plugin to - add recommended packages by adding the ``recommended`` attribute, - e.g.: + The default behavior of the Packages plugin is to not make any + assumptions about which packages you want to have added automatically + [#f1]_. For that reason, neither **Recommended** nor **Suggested** + packages are added as dependencies by default. You will notice + that the default behavior for apt is to add Recommended packages as + dependencies. You can configure the Packages plugin to add recommended + packages by adding the ``recommended`` attribute, e.g.: .. code-block:: xml @@ -221,6 +220,14 @@ something like this:: .. warning:: You must regenerate the Packages cache when adding or removing the recommended attribute. + .. [#f1] Bcfg2 will by default add **Essential** packages to the + client specification. You can disable this behavior by + setting the ``essential`` attribute to *false*: + + .. code-block:: xml + + + Yum sources can be similarly specified:: -- cgit v1.2.3-1-g7c22