summaryrefslogtreecommitdiffstats
path: root/doc/server/plugins/generators/packages.txt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/server/plugins/generators/packages.txt')
-rw-r--r--doc/server/plugins/generators/packages.txt19
1 files changed, 12 insertions, 7 deletions
diff --git a/doc/server/plugins/generators/packages.txt b/doc/server/plugins/generators/packages.txt
index d1a68b16e..90cd19de4 100644
--- a/doc/server/plugins/generators/packages.txt
+++ b/doc/server/plugins/generators/packages.txt
@@ -15,6 +15,8 @@ information, Packages delegates control of package version information to
the underlying package manager, installing the latest version available
through those channels.
+.. _server-plugins-generators-packages-magic-groups:
+
"Magic Groups"
==============
@@ -152,14 +154,15 @@ like this:
</Sources>
.. note::
+
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 following line immediately following the URL:
+ 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 following line immediately
+ following the **URL**:
.. versionadded:: 1.1.0
@@ -184,6 +187,8 @@ Yum sources can be similarly specified:
</YUMSource>
</Sources>
+For sources with a **URL** tag, the **Version** tag is also necessary.
+
.. note:: There is also a RawURL syntax for specifying APT or YUM sources that
don't follow the conventional layout:
@@ -268,7 +273,7 @@ Validation
==========
A schema for Packages/config.xml is included; config.xml can be validated
-using ``bcfg2-repo-validate``.
+using ``bcfg2-lint``.
.. note:: The schema requires that elements be specified in the above order.