[Dbconfig-common-devel] dbconfig-common/doc dbconfig-common-using.html, 1.16, 1.17

[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-serv5282/doc

Modified Files:
	dbconfig-common-using.html 
Log Message:
note that the second of these is not yet fully tested, so no release
just yet.  

    - add support for 'template' output format in dbc_generate_include.
    - dbc no longer provides preinst hooks, as we can't promise
      dbconfig-common will be there without pre-depends.  turns out
      there was a more graceful way to handle what we wanted to do
      in there anyway.  also updated example packages accordingly.
      thanks to Miguel (as well as Marc 'HE' Brockschmidt)
      for finding this (closes: #323620).



Index: dbconfig-common-using.html
===================================================================
RCS file: /cvsroot/dbconfig-common/dbconfig-common/doc/dbconfig-common-using.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- dbconfig-common-using.html	24 Aug 2005 22:38:39 -0000	1.16
+++ dbconfig-common-using.html	24 Aug 2005 23:37:12 -0000	1.17
@@ -63,12 +63,15 @@
 <h4> putting hooks into the maintainer scripts </h4>
 
 <p>
-in the postinst, preinst, prerm, and postrm scripts for your package,
+in the postinst, prerm, and postrm scripts for your package,
 you will need to source the libraries which perform most of the work
-for you.  if you are not currently using debconf in your package,
-you will be now, and the debconf libraries need to be sourced first.
-for example, here's an what it should look like in a postinst script
-for an imaginary "foo-mysql" package:
+for you (you do not need to do so in your preinst script).  if you are
+not currently using debconf in your package, you will be now, and the
+debconf libraries need to be sourced first.  you will need to depend
+on debconf explicitly, and either use dh_installdebconf or otherwise
+install your <code>config</code> script into your deb file if you're
+not already doing so.  for example, here's an what it should look like
+in a postinst script for an imaginary "foo-mysql" package:
 
 <pre>
 <code>