[Dbconfig-common-devel] dbconfig-common/doc dbconfig-common-using.html, 1.13, 1.14

[seanius at haydn.debian.org]

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

Modified Files:
	dbconfig-common-using.html 
Log Message:
documentation update about debugging

Index: dbconfig-common-using.html
===================================================================
RCS file: /cvsroot/dbconfig-common/dbconfig-common/doc/dbconfig-common-using.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- dbconfig-common-using.html	11 Jul 2005 04:23:01 -0000	1.13
+++ dbconfig-common-using.html	29 Jul 2005 06:29:20 -0000	1.14
@@ -43,6 +43,7 @@
   <li><a href="#updates"> database changes in new versions of your package </a>
   <li><a href="#multidb"> packages that support multiple types of databases </a>
   <li><a href="#defaults"> hinting defaults and advanced control of configuration/installation </a>
+  <li><a href="#debugging"> debugging problems with dbconfig-common </a>
   </ul>
 </ul>
 
@@ -365,5 +366,28 @@
 <td>arguments passed directly to dbconfig-load-include
 <td>empty
 </table>
+
+<a name="debugging">
+<h4> debugging problems with dbconfig-common
+</a>
+
+<p>
+in the event that your package is having trouble working with
+dbconfig-common, the first thing you should try is to export and set the
+shell variable <code>dbc_debug</code> to a nonempty value before
+installing your package.  this will provide a slightly larger amount of
+information about what's going on.
+
+<p>
+in the event that this does not provide enough information, the next thing
+to do will provide much, much, more information; enough that you will
+probably want to redirect stderr into a temporary output file.  in the
+file <code>/usr/share/dbconfig-common/dpkg/common</code>, uncomment the
+<code>set -x</code> line near the top of the file.  this will show you
+all the shell commands and logic as they are executed.  if you have a
+good idea of where the problem is occurring, you can also insert your
+own <code>set -x</code> lines elsewhere followed by <code>set +x</code>
+lines to reduce the amount of input.
+
 </body>
 </html>