[Webapps-common-discuss] webapps-common/doc webapps-common.sgml, 1.3, 1.4

[seanius at haydn.debian.org]

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

Modified Files:
	webapps-common.sgml 
Log Message:
big ol' chunk a work.  almost presentable again :)


Index: webapps-common.sgml
===================================================================
RCS file: /cvsroot/webapps-common/webapps-common/doc/webapps-common.sgml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- webapps-common.sgml	19 Oct 2005 17:58:28 -0000	1.3
+++ webapps-common.sgml	1 Apr 2006 12:14:25 -0000	1.4
@@ -99,22 +99,16 @@
 	<sect id="simple">The simplest example - "simple"
 		<p>
 		In the simplest case, you can activate webapps-common by
-		adding two lines in each of your maintainer scripts that
-		source the appropriate webapps-common shell script library,
-		and call the <var>wc_go</var> function.  For example, the
-		config script should contain:
+		adding two lines in your config, prerm, postinst, and
+		postrm maintainer scripts that source the appropriate
+		webapps-common shell script library, and call the
+		<var>wc_go</var> function.  For example, the config
+		script should contain:
 		<example>
 		. /usr/share/debconf/confmodule
 		. /usr/share/webapps-common/dpkg/config
 		wc_go PACKAGE $@
 		</example>
-		<p>
-		TODO: do we really need to do this in the preinst?  I
-		don't think so.  If we did, you'd have to pre-depend,
-		which we don't want to do.  we had the same problem
-		in dbconfig-common and it was solved by removing the
-		need for a preinst hook altogether.  was a problem in
-		dbconfig-common
 	<sect id="inline">Using "inline" configuration
 		<p>
 		If the application your packaging requires some
@@ -194,9 +188,10 @@
 		If you would like to see working examples of packages
 		currently using webapps-common, grab the latest
 		webapps-common source from alioth, and look in the
-		examples subdirectory.  This directory is a debian
-		source package that generates example packages implementing
-		each of the above installation methods.
+		examples subdirectory.  This directory contains debian
+		source packages that generates packages implementing
+		each of the above installation methods.  just run
+		the included buildpackages.sh script to generate them.
 
 <chapt id="advanced">Advanced Techniques and Concepts
 	<p> TODO