cvs: peardoc /en/pyrus/about whatis.xml /en/pyrus/developers pear.xml pear2.xml pecl.xml

cellog		Thu Jul  2 17:24:13 2009 UTC

  Modified files:              
    /peardoc/en/pyrus/about	whatis.xml 
    /peardoc/en/pyrus/developers	pear.xml pear2.xml pecl.xml 
  Log:
  finish docs for pyrus alpha 0.1.0 - more work needs to be done on describing API, and classes need to be moved to namespaces in the docs when that happens in the code
  but the stuff you need for non-power users is all there ready to go
  
http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/about/whatis.xml?r1=1.1&r2=1.2&diff_format=u
Index: peardoc/en/pyrus/about/whatis.xml
diff -u peardoc/en/pyrus/about/whatis.xml:1.1 peardoc/en/pyrus/about/whatis.xml:1.2
--- peardoc/en/pyrus/about/whatis.xml:1.1	Fri Jun 26 05:22:01 2009
+++ peardoc/en/pyrus/about/whatis.xml	Thu Jul  2 17:24:13 2009
@@ -18,7 +18,9 @@
    <link linkend="channels">channels</link>.
   </para>
   <para>
-   This documentation is a work in progress.
+   Pyrus represents the cumulative effort of years of work, experience with the
+   PEAR Installer since its inception in 1999, and feedback from users like you.
+   We are very proud to present the best installation tool for PHP.
   </para>
  </section>
 </section>
http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/developers/pear.xml?r1=1.1&r2=1.2&diff_format=u
Index: peardoc/en/pyrus/developers/pear.xml
diff -u peardoc/en/pyrus/developers/pear.xml:1.1 peardoc/en/pyrus/developers/pear.xml:1.2
--- peardoc/en/pyrus/developers/pear.xml:1.1	Thu Jun 18 04:50:40 2009
+++ peardoc/en/pyrus/developers/pear.xml	Thu Jul  2 17:24:13 2009
@@ -4,6 +4,12 @@
 
  <section xml:id="pyrus.developers.pear.intro">
   <info><title>Introduction</title></info>
-  <para>This is a work in progress.</para>
+  <para>
+   Using Pyrus to manage your existing PEAR package is simple, although not
+   as easy as managing a PEAR2 package or PECL extension.  Generally speaking,
+   the command you will take advantage of the most is the
+   <link linkend="pyrus.commands.package">package</link>
+   command, which can be used to create the release needed.
+  </para>
  </section>
 </section>
http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/developers/pear2.xml?r1=1.1&r2=1.2&diff_format=u
Index: peardoc/en/pyrus/developers/pear2.xml
diff -u peardoc/en/pyrus/developers/pear2.xml:1.1 peardoc/en/pyrus/developers/pear2.xml:1.2
--- peardoc/en/pyrus/developers/pear2.xml:1.1	Thu Jun 18 04:50:40 2009
+++ peardoc/en/pyrus/developers/pear2.xml	Thu Jul  2 17:24:13 2009
@@ -4,6 +4,14 @@
 
  <section xml:id="pyrus.developers.pear2.intro">
   <info><title>Introduction</title></info>
-  <para>This is a work in progress.</para>
+  <para>
+   Pyrus is particularly well-suited to maintaining a PEAR2 package, and can
+   be used to easily create a package.xml with the <link linkend="pyrus.commands.make">make</link>
+   command.  Once the requisite files are in place for this command, creating
+   a release is as simple as
+  </para>
+  <para>
+   <screen>php -dphar.readonly=0 pyrus.phar make -pphar,tar,tgz,zip</screen>
+  </para>
  </section>
 </section>
http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/developers/pecl.xml?r1=1.2&r2=1.3&diff_format=u
Index: peardoc/en/pyrus/developers/pecl.xml
diff -u peardoc/en/pyrus/developers/pecl.xml:1.2 peardoc/en/pyrus/developers/pecl.xml:1.3
--- peardoc/en/pyrus/developers/pecl.xml:1.2	Thu Jul  2 17:15:12 2009
+++ peardoc/en/pyrus/developers/pecl.xml	Thu Jul  2 17:24:13 2009
@@ -18,6 +18,10 @@
    even look at package.xml, greatly simplifying the lives of PECL extension
    developers.
   </para>
+  <para>
+   In addition, the <link linkend="pyrus.commands.runphpt">run-phpt</link>
+   command can be used to run all the extension's phpt test files.
+  </para>
  </section>
  <section xml:id="pyrus.developers.pecl.newpackage">
   <title>Creating a new PECL package with Pyrus</title>