[Dbconfig-common-devel] dbconfig-common/doc dbconfig-common-using.html,1.11,1.12

[seanius@haydn.debian.org]

Update of /cvsroot/dbconfig-common/dbconfig-common/doc
In directory haydn:/org/alioth.debian.org/chroot/home/users/seanius/tmp/cvs-serv7828

Modified Files:
	dbconfig-common-using.html 
Log Message:
documentation fixes and clarifications

Index: dbconfig-common-using.html
===================================================================
RCS file: /cvsroot/dbconfig-common/dbconfig-common/doc/dbconfig-common-using.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -d -r1.11 -r1.12
--- dbconfig-common-using.html	19 May 2005 01:48:33 -0000	1.11
+++ dbconfig-common-using.html	21 May 2005 15:59:56 -0000	1.12
@@ -168,17 +168,24 @@
 <p>
 if your package is already part of debian, dbconfig-common provides some
 support to load pre-existing settings from a specified config by setting
-two variables: <code>dbconfig_first_version</code> and <code>dbconfig_load_include</code>.  
+two variables: <code>dbc_first_version</code> and <code>dbc_load_include</code>.
 </p>
 
 <p>
-<code>dbconfig_load_include</code> should be
-specified in the config script and be of the format
-<code>format:inputfile</code>. <code>dbconfig_first_version</code> should
-be specified in both the config <i>and</i> postinst scripts, and should
-contain the first version in which dbconfig-common was introduced.
-when the package is installed, if it is being upgraded from a version less
-than this value it will attempt to bootstrap itself with the values.  
+<code>dbc_load_include</code> should be specified in the config script
+and be of the format <code>format:inputfile</code>. <code>format</code> is
+one of the languages understood by dbconfig-load-include, and
+<code>inputfile</code> is either the config file in <code>format</code>
+language, or a script file in <code>format</code> language that otherwise
+determines the values and sets them.
+</p>
+
+<p>
+<code>dbc_first_version</code> should be specified in both the config
+<i>and</i> postinst scripts, and should contain the first version in
+which dbconfig-common was introduced.  when the package is installed,
+if it is being upgraded from a version less than this value it will
+attempt to bootstrap itself with the values.
 </p>
 
 <a name="updates">