From e7f6dd5dc96c8d4d8043c148c1a4c6e2b59fa99b Mon Sep 17 00:00:00 2001 From: Sol Jerome Date: Wed, 27 Jul 2011 13:53:28 -0500 Subject: doc: Provide examples of abstract and literal specifications Signed-off-by: Sol Jerome --- doc/architecture/server.txt | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'doc/architecture/server.txt') diff --git a/doc/architecture/server.txt b/doc/architecture/server.txt index 1341f9e0a..d58b6629f 100644 --- a/doc/architecture/server.txt +++ b/doc/architecture/server.txt @@ -46,6 +46,12 @@ is tailored for the client. This process consists of the following steps: include a name. These configuration entries are grouped into bundles, which document installation time interdependencies. + Here is an example of an abstract configuration entry: + + .. code-block:: xml + + + * **Configuration Binding** The abstract configuration determines the structure of the client @@ -63,3 +69,10 @@ is tailored for the client. This process consists of the following steps: specification. This specification is complete and comprehensive; the client doesn't need to process it at all in order to use it. It also represents the totality of the configuration specified for the client. + + Here is the entry from above once it has been bound to its literal + specification (In this case, using the Packages plugin). + + .. code-block:: xml + + -- cgit v1.2.3-1-g7c22