[Webapps-common-discuss] webapps-common/doc PHP-Policy-Manual-DRAFT.sgml, 1.4, 1.5

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

Modified Files:
	PHP-Policy-Manual-DRAFT.sgml 
Log Message:
some misc changes, see changelog


Index: PHP-Policy-Manual-DRAFT.sgml
===================================================================
RCS file: /cvsroot/webapps-common/webapps-common/doc/PHP-Policy-Manual-DRAFT.sgml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- PHP-Policy-Manual-DRAFT.sgml	4 Aug 2005 10:38:31 -0000	1.4
+++ PHP-Policy-Manual-DRAFT.sgml	24 Nov 2005 10:28:52 -0000	1.5
@@ -217,6 +217,16 @@
 			for packages that depend on a specific
 			version of php libraries can be placed in
 			<file>/usr/share/php<var>PHPVERSION</var></file>
+		<sect id="php-libs-naming">Package Naming Requirements for php libraries
+		<p>
+			Debianized PHP libraries should be prefixed to identify themselves
+			as such.  The naming scheme should follow that of other languages
+			(such as perl, ruby, and python) and name packages in the form
+			<package>lib<var>PEARLIBRARYNAME</var>-php</package>.
+			Optionally, if the php library only works with a specific
+			version of php
+			<package>lib<var>PEARLIBRARYNAME</var>-php<var>PHPVERSION</var></package>.
+			would also be acceptable.
 
 		<sect id="php-libs-pear">Requirements for PHP PEAR libraries
 		<p>
@@ -236,9 +246,18 @@
 			<package>php-<var>PEARLIBRARYNAME</var></package>.
 		<p>
 			XXX should this be <package>php-pear-<var>PEARLIBRARYNAME</var></package>?
+		<p>
+			XXX should this be <package>libpear-<var>PEARLIBRARYNAME</var>-php</package>?
+		<p>
+			XXX should this be <package>lib<var>PEARLIBRARYNAME</var>-pear-php</package>?
+		<p>
+			XXX should this be no different from normal libraries?
 		<sect1 id="php-libs-pear-extra">Other installation requirements for PEAR packages
 		<p>
-			PHP PEAR library packages must also register and unregister themselves in the pear package management system.  this can be done by adding the following code in the packages postinst script:
+			PHP PEAR library packages must also register
+			and unregister themselves in the pear package
+			management system.  this can be done by adding the
+			following code in the packages postinst script:
 			<example>
 			pear install -r package.xml
 			</example>