[Webapps-common-discuss] webapps-common/doc Webapps-Pear-Policy-Manual-DRAFT.html, 1.2, 1.3

Wed Aug 3 15:59:01 UTC 2005

Update of /cvsroot/webapps-common/webapps-common/doc
In directory haydn:/tmp/cvs-serv8263

Modified Files:
	Webapps-Pear-Policy-Manual-DRAFT.html 
Log Message:
minor fixes


Index: Webapps-Pear-Policy-Manual-DRAFT.html
===================================================================
RCS file: /cvsroot/webapps-common/webapps-common/doc/Webapps-Pear-Policy-Manual-DRAFT.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3

--- Webapps-Pear-Policy-Manual-DRAFT.html	18 Jul 2005 14:32:04 -0000	1.2
+++ Webapps-Pear-Policy-Manual-DRAFT.html	3 Aug 2005 15:58:58 -0000	1.3
@@ -1,5 +1,7 @@
 <!-- $Id$ -->
 
+<html>
+<body>
 <h1>1. Policy for PEAR modules</h1>
 
 <h2>1.1 Package name</h2>
@@ -20,7 +22,7 @@
 
 <p>
 You may use <tt>pear install -r package.xml</tt> in <tt>postinst</tt> and
-<tt>pear uninstall -r PEAR_MODULE_NAME</tt> in <tt>prerm</tt> to achieve that
+<tt>pear uninstall -r PEAR_MODULE_NAME</tt> in <tt>prerm</tt> to achieve that.
 </p>
 
 <h2>1.3 Other Packaging Notes</h2>
@@ -28,7 +30,7 @@
 <ul>
   <li>you should write a debian/watch file looking like :
   <div class="src">
-    version=2<br />
+    version=3<br />
     http://pear.php.net/package/&lt;package&gt;/download&nbsp;/get/&lt;package&gt;-([\d.]+)\.tgz
   </div>
   </li>
@@ -62,23 +64,29 @@
   <li>to not break pear's own packaging system</li>
 </ul>
 
+<p>The following instructions outline how to manually create a new PEAR module
+package. Note that the Debian package <tt>dh-make-php</tt> can do this for you
+automatically.</p>
+
 <h2>2.1 Create the debian/ dir</h2>
 
 <p>First, get the official pear module you want to package using the
-<tt>pear</tt> command from the <tt>php4-pear</tt> package</p>
+<tt>pear</tt> command from the <tt>php4-pear</tt> package (unless
+the most recent release is a beta release, in which case the current
+stable release must be manually downloaded):</p>
 <div class="src">
   ~$ <strong>pear download MDB</strong><br />
   File MDB-1.3.0.tgz downloaded (218957 bytes)
 </div>
 
 <p>
-And then prepare our deb-source tree : rename the tgz into a
+And then prepare our deb-source tree : symlink the tgz into a
 package_version.orig.tar.gz, and unpack it.
 </p>
 <div class="src">
-  ~$ <strong>mv MDB-1.3.0.tgz php-mdb_1.3.0.orig.tar.gz</strong><br />
-  ~$ <strong>mkdir php-mdb</strong><br />
-  ~$ <strong>cd php-mdb</strong><br />
+  ~$ <strong>ln -s MDB-1.3.0.tgz php-mdb_1.3.0.orig.tar.gz</strong><br />
+  ~$ <strong>mkdir php-mdb-1.3.0</strong><br />
+  ~$ <strong>cd php-mdb-1.3.0</strong><br />
   ~/php-mdb$ <strong>tar xzf ../php-mdb_1.3.0.orig.tar.gz</strong><br />
   ~/php-mdb$ <strong>mkdir debian</strong><br />
   ~/php-mdb$ <strong>echo 4 &gt; debian/compat</strong><br />
@@ -88,7 +96,9 @@
 
 <p>I know that to decompress the orig.tar.gz into a subdir seems to be awkward,
 but in fact, it has a file (<tt>package.xml</tt>) that is at the toplevel of the
-archive, and dpkg knows how to deal with it alone ! big good boy ;)</p>
+archive, and dpkg knows how to deal with it alone ! big good boy ;). This also
+has the advantage that it allows <tt>uupdate</tt> to work properly with the
+package, and that the orig.tar.gz is an unchanged copy of the original archive.</p>
 
 <h2>2.2 Create the debian/rules script</h2>
 
@@ -288,4 +298,7 @@
   files</li>
 </ul>
 
+</body>
+</html>
+
 <!-- vim:set et sw=2 sts=2 sws=2: -->


