From 6efebfd9644039e76efa9ea25dc5e684981f707d Mon Sep 17 00:00:00 2001 From: Sol Jerome Date: Tue, 9 Mar 2010 17:02:53 +0000 Subject: doc: Add note to summarize Packages group memberships Signed-off-by: Sol Jerome git-svn-id: https://svn.mcs.anl.gov/repos/bcfg/trunk/bcfg2@5758 ce84e21b-d406-0410-9b95-82705330c041 --- doc/server/plugins/generators/packages.txt | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/server/plugins/generators/packages.txt b/doc/server/plugins/generators/packages.txt index 1b12e88fd..6158ee8b2 100644 --- a/doc/server/plugins/generators/packages.txt +++ b/doc/server/plugins/generators/packages.txt @@ -53,13 +53,18 @@ architecture groups (i386 or amd64). Memberships in architecture groups is needed so that Packages can map software sources to clients. There is no other way to handle this than -to impose +to impose membership in the appropriate architecture group. When multiple sources are specified, clients are associated with each source to which they apply (based on group memberships, as described above). Packages and dependencies are resolved from all applicable sources. +.. note:: To recap, a client needs to be a member of the **OS Group**, + **Architecture** group, and any other groups defined in your + ``Packages/config.xml`` file in order for the client to be + associated to the proper sources. + Setup ===== -- cgit v1.2.3-1-g7c22