cvs: peardoc /en/guide/developers/package2 dependencies.xml /en/pyrus commands.xml /en/pyrus/commands build.xml channeladd.xml channeldel.xml channeldiscover.xml configshow.xml download.xml help.xml info.xml install.xml listchannels.xml listpackages.xml listupgrades.xml make.xml mypear.xml package.xml pickle.xml remotelist.xml runphpt.xml runscripts.xml set.xml uninstall.xml upgrade.xml upgraderegistry.xml

http://cvs.php.net/viewvc.cgi/peardoc/en/guide/developers/package2/dependencies.xml?r1=1.7&r2=1.8&diff_format=u
Index: peardoc/en/guide/developers/package2/dependencies.xml
diff -u peardoc/en/guide/developers/package2/dependencies.xml:1.7 peardoc/en/guide/developers/package2/dependencies.xml:1.8
--- peardoc/en/guide/developers/package2/dependencies.xml:1.7	Thu Oct  9 15:16:18 2008
+++ peardoc/en/guide/developers/package2/dependencies.xml	Fri Jun 26 18:10:51 2009
@@ -7,36 +7,24 @@
  <refsection xml:id="guide.developers.package2.dependencies.intro"><info><title>Introduction to dependencies in package.xml 2.0</title></info> 
   
   <para>
-   Dependencies are the most difficult aspect of programming.  Using code written by other people
-   can be a nightmare without simple ways to control bugs and API changes.  Arguably, the handling
-   of dependencies is PEAR's greatest strength, although there are many other nice features.  Regardless
-   of your personal opinion of the importance of dependencies, it is crucial to understand how to
-   specify a dependency, and the different ways to ensure that your package is only used on systems
-   that support it.
+   Dependencies can be tricky to manage.  Using code written by other people
+   requires a robust and simple mechanism to manage the risk of breaking your code
+   because of bugs in the external package, or worse, an unexpected API change.
+   PEAR excels at dependency handling, which mitigates these risks.
+   As a PEAR developer, it is crucial to understand how to
+   specify a dependency on other packages as well as the system requirements of
+   your package.
   </para>
   <para>
-   In package.xml 1.0, dependencies were relatively simple, but at the cost of usefulness.  Specifying
+   In package.xml 1.0, dependencies are relatively simple, but not as powerful.  Specifying
    a dependency on a package for applications was actually dangerous.  If you wished to limit an installed
    version of a package to a single version, it would mean preventing upgrade at any cost.  package.xml
    2.0 provides a simple way to enforce stricter dependency versioning without making upgrades onerous.
   </para>
   <para>
-   In package.xml 1.0, dependencies on PHP extensions like <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.pecl;">PECL</link>
-   extensions was near to a disaster.  Extensions had to be present in the php.ini and loaded in
-   memory in order to validate as being installed.  This is often impossible, as a different php.ini
-   is used for a production website versus the php.ini used for the pear installer.  With package.xml
-   2.0, dependencies on a PECL-like extension is simple and straightforward, and only requires that
-   the package be installed, and not that the extension be present in memory, although an older
-   style extension dependency is also supported.
-  </para>
-  <para>
    package.xml 1.0 supports two kinds of dependencies, required and optional.  package.xml 2.0
    also supports these two dependency types, but introduces a new kind of dependency concept: an
-   optional dependency group.  Dependency groups define a feature set.  Instead of thinking
-   &quot;This package optionally depends on Net_FTP and optionally depends on Log&quot; think
-   &quot;To remotely install packages, I need the remoteinstall feature, which needs Net_FTP
-   and the Log package&quot;.  This grouping allows defining sets of packages and extensions that
-   comprise a feature and must be installed all at once for the feature to function properly.
+   optional dependency group (documented <link linkend="guide.developers.package2.dependencies.groups">here</link>).  
   </para>
   <para>
    package.xml 1.0 only supported php, package, and extension dependencies.  package.xml 2.0
@@ -77,11 +65,10 @@
 <dependencies>
  <required>
   <pearinstaller>
-   <min>1.4.0a7</min>
+   <min>1.4.8</min>
   </pearinstaller>
   <php>
    <min>4.2.0</min>
-   <max>6.0.0</max>
   </php>
   <package>
    <name>Archive_Tar</name>
@@ -106,6 +93,38 @@
     &lt;php&gt; dependencies.
    </para>
   </refsection>
+  <refsection xml:id="guide.developers.package2.dependencies.groups">
+   <info><title>Optional Dependency Groups</title></info>
+   <para>
+    Optional dependency groups define feature sets that are not required, but
+    should be installed in a block.  These feature sets consist of &lt;package&gt;
+    and &lt;extension&gt; dependencies.  For instance, if a package can optionally
+    perform operations on a remote shell, it would create an optional dependency
+    group named <literal>remoteshell</literal> with dependencies on the
+    <literal>ssh2</literal> PECL extension and the (fictional)
+    <literal>SSH_RemoteShell</literal> package.  The dependency group could look
+    like this in package.xml:
+   </para>
+   <para>
+    <programlisting role="xml">
+     <![CDATA[
+<group name="remoteshell" hint="Add support for Remote Shell Operations">
+ <package>
+  <name>SSH_RemoteShell</name>
+  <channel>pear.php.net</channel>
+ </package>
+ <extension>
+  <name>ssh2</name>
+ </extension>
+</group>
+     ]]>
+    </programlisting>
+   </para>
+   <para>
+    To install this dependency group, the user would simply use
+    <literal>pear install Packagename#remoteshell</literal>.
+   </para>
+  </refsection>
   <refsection xml:id="guide.developers.package2.dependencies.pearinstaller"><info><title>&lt;pearinstaller&gt; dependencies</title></info>
    
    <para>
http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands.xml?r1=1.1&r2=1.2&diff_format=u
Index: peardoc/en/pyrus/commands.xml
diff -u peardoc/en/pyrus/commands.xml:1.1 peardoc/en/pyrus/commands.xml:1.2
--- peardoc/en/pyrus/commands.xml:1.1	Fri Jun 26 05:22:01 2009
+++ peardoc/en/pyrus/commands.xml	Fri Jun 26 18:10:51 2009
@@ -1,14 +1,43 @@
 <?xml version="1.0" encoding="utf-8"?>
-<chapter xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands">
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:phd="http://www.php.net/ns/phd" version="lillet" xml:id="pyrus.commands">
   <info>
    <title>Commands available in Pyrus</title>
    <author><personname><firstname>Gregory</firstname><surname>Beaver</surname></personname></author>
    <date>2009-06-25</date>
   </info>
 
+  <!-- this thing does not work whatsoever. -->
+  <phd:toc phd:toc-depth="3" phd:element="pyrus.commands"/>
   <simpara>
-   Commands available for Pyrus.  This documentation is a work in progress.
+   Commands available for the Pyrus command-line script.
   </simpara>
 
   &pyrus.commands.install;
+  &pyrus.commands.upgrade;
+  &pyrus.commands.uninstall;
+  &pyrus.commands.runscripts;
+  &pyrus.commands.download;
+
+  &pyrus.commands.channeladd;
+  &pyrus.commands.channeldiscover;
+  &pyrus.commands.channeldel;
+
+  &pyrus.commands.info;
+  &pyrus.commands.listpackages;
+  &pyrus.commands.listchannels;
+  &pyrus.commands.remotelist;
+  &pyrus.commands.listupgrades;
+  &pyrus.commands.upgraderegistry;
+
+  &pyrus.commands.configshow;
+  &pyrus.commands.set;
+  &pyrus.commands.mypear;
+
+  &pyrus.commands.runphpt;
+  &pyrus.commands.make;
+  &pyrus.commands.package;
+
+  &pyrus.commands.pickle;
+  &pyrus.commands.build;
+  
  </chapter>
http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/install.xml?r1=1.1&r2=1.2&diff_format=u
Index: peardoc/en/pyrus/commands/install.xml
diff -u peardoc/en/pyrus/commands/install.xml:1.1 peardoc/en/pyrus/commands/install.xml:1.2
--- peardoc/en/pyrus/commands/install.xml:1.1	Fri Jun 26 05:22:01 2009
+++ peardoc/en/pyrus/commands/install.xml	Fri Jun 26 18:10:52 2009
@@ -4,6 +4,182 @@
 
  <section xml:id="pyrus.commands.install.intro">
   <info><title>Introduction</title></info>
-  <para>This is a work in progress.</para>
+  <para>
+   The install command is used to install packages.  Unlike
+   <link linkend="pyrus.commands.upgrade">upgrade</link>, the install command will
+   only install new packages.
+  </para>
+  <para>
+   Install recognizes several different ways of specifying a package:
+   <table>
+    <title>Ways of specifying a package for installation</title>
+    <tgroup cols="3">
+     <thead>
+      <row>
+       <entry>Package type</entry>
+       <entry>Local/Remote</entry>
+       <entry>Example</entry>
+      </row>
+     </thead>
+
+     <tbody>
+      <row>
+       <entry><literal>package.xml</literal> file</entry>
+       <entry>Local</entry>
+       <entry><userinput>php pyrus.phar install /path/to/package.xml</userinput></entry>
+      </row>
+      <row>
+       <entry>Package release archive</entry>
+       <entry>Local</entry>
+       <entry><userinput>php pyrus.phar install /path/to/PackageName-1.2.3.tgz</userinput></entry>
+      </row>
+      <row>
+       <entry>Static url</entry>
+       <entry>Remote</entry>
+       <entry><userinput>php pyrus.phar install http://example.com/PackageName-1.2.3.tgz</userinput></entry>
+      </row>
+      <row>
+       <entry>Abstract package</entry>
+       <entry>Remote</entry>
+       <entry><userinput>php pyrus.phar install PackageName</userinput></entry>
+      </row>
+     </tbody>
+    </tgroup>
+   </table>
+  </para>
+  <para>
+   The first three ways of specifying a package are concrete: the package name
+   always refers to one and only one package.  Abstract packages are more
+   flexible, and there are several ways of requesting a package
+   <table>
+    <title>Ways of specifying an abstract package for installation</title>
+    <tgroup cols="2">
+     <thead>
+      <row>
+       <entry>Example</entry>
+       <entry>Description</entry>
+      </row>
+     </thead>
+
+     <tbody>
+      <row>
+       <entry><literal>PackageName-1.2.3</literal></entry>
+       <entry>
+        This forces Pyrus to download version <literal>1.2.3</literal> of
+        package <literal>PackageName</literal>, but will will attempt to download
+        a release in one of the following file formats, in this order:
+        <orderedlist>
+         <listitem><simpara>phar</simpara></listitem>
+         <listitem><simpara>tgz (only if zlib extension is enabled)</simpara></listitem>
+         <listitem><simpara>tar</simpara></listitem>
+         <listitem><simpara>zip</simpara></listitem>
+        </orderedlist>
+       </entry>
+      </row>
+      <row>
+       <entry><literal>PackageName-alpha</literal></entry>
+       <entry>
+        This causes Pyrus to download the latest version of
+        package <literal>PackageName</literal> that is <literal>alpha</literal>
+        stability or better (the hierarchy of stabilities is <literal>devel</literal>,
+        <literal>alpha</literal>, <literal>beta</literal>, <literal>stable</literal>).
+        After finding a matching version, it will attempt to download a release
+        in one of the following file formats, in this order:
+        <orderedlist>
+         <listitem><simpara>phar</simpara></listitem>
+         <listitem><simpara>tgz (only if zlib extension is enabled)</simpara></listitem>
+         <listitem><simpara>tar</simpara></listitem>
+         <listitem><simpara>zip</simpara></listitem>
+        </orderedlist>
+       </entry>
+      </row>
+      <row>
+       <entry><literal>PackageName</literal></entry>
+       <entry>
+        This causes Pyrus to download the latest version of
+        package <literal>PackageName</literal> that is <literal>preferred_state</literal>
+        (configuration variable)
+        stability or better (the hierarchy of stabilities is <literal>devel</literal>,
+        <literal>alpha</literal>, <literal>beta</literal>, <literal>stable</literal>).
+        After finding a matching version, it will attempt to download a release
+        in one of the following file formats, in this order:
+        <orderedlist>
+         <listitem><simpara>phar</simpara></listitem>
+         <listitem><simpara>tgz (only if zlib extension is enabled)</simpara></listitem>
+         <listitem><simpara>tar</simpara></listitem>
+         <listitem><simpara>zip</simpara></listitem>
+        </orderedlist>
+        The <literal>preferred_state</literal> configuration variable can be seen
+        with the <link linkend="pyrus.commands.configshow">config-show</link>
+        command.
+       </entry>
+      </row>
+      <row>
+       <entry><literal>PackageName#groupname</literal></entry>
+       <entry>
+        This causes Pyrus to download and install a release of Pyrus as specified
+        above, and it also causes Pyrus to download and install the contents
+        of the <literal>groupname</literal> dependency group (dependency groups
+        are documented <link linkend="guide.developers.package2.dependencies.groups">here</link>).
+       </entry>
+      </row>
+     </tbody>
+    </tgroup>
+   </table>
+  </para>
+ </section>
+ <section xml:id="pyrus.commands.install.optionaldeps">
+  <title>--optionaldeps</title>
+  <para>
+   By default, required package dependencies are also installed.  To also
+   automatically install optional dependencies (not dependency groups, but
+   dependencies specified using the &lt;optional&gt; tag in package.xml),
+   pass the <literal>-o</literal> or <literal>--optionaldeps</literal> option
+   to the install command:
+  </para>
+  <para>
+   <screen>php pyrus.phar install -o PackageName</screen>
+  </para>
+ </section>
+ <section xml:id="pyrus.commands.install.plugins">
+  <title>--plugin</title>
+  <para>
+   Plugins (documented <link linkend="pyrus.plugins">here</link>) must be explicitly
+   installed with the <literal>-p</literal> or <literal>--plugin</literal> option.
+   Plugins are installed into the location specified by the <literal>plugins_dir</literal>
+   configuration variable, which defaults to the same location that the user
+   configuration file is located (<literal>$HOME/.pear</literal> in unix,
+   <literal>&lt;My Documents&gt;\pear</literal> on windows).
+  </para>
+  <para>
+   <screen>php pyrus.phar install -p PEAR2_Pyrus_Developer</screen>
+  </para>
+ </section>
+ <section xml:id="pyrus.commands.install.packagingroot">
+  <title>--packagingroot</title>
+  <para>
+   Developers packaging RPMs or other forms of distribution for OS vendors
+   should use the <literal>-r</literal> or <literal>--packagingroot</literal>
+   option to install a package into a subdirectory for creating the RPM.
+  </para>
+  <para>
+   <screen>php pyrus.phar install -r /home/myuser/package PackageName</screen>
+  </para>
+  <para>
+   For the example above, if the default Pyrus installation is in
+   <literal>/usr/local/lib/pear</literal>, all files will be installed
+   into <literal>/home/myuser/package/usr/local/lib/pear</literal>.  Another
+   way of understanding this is that the packagingroot option instructs
+   Pyrus to treat <literal>/home/myuser/package</literal> as if it were the
+   root directory <literal>/</literal>.
+  </para>
+  <para>
+   Developers packaging RPMs or other forms of distribution for OS vendors
+   should use the <literal>-r</literal> or <literal>--packagingroot</literal>
+   option to install a package into a subdirectory for creating the RPM.
+  </para>
+  <para>
+   <screen>php pyrus.phar install -r /home/myuser/package PackageName</screen>
+  </para>
  </section>
 </section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/build.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/build.xml
+++ peardoc/en/pyrus/commands/build.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.build">
 <info><title>build - build a PECL PHP extension package</title></info>

 <section xml:id="pyrus.commands.build.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/channeladd.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/channeladd.xml
+++ peardoc/en/pyrus/commands/channeladd.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.channeladd">
 <info><title>channel-add - add a channel by its channel.xml</title></info>

 <section xml:id="pyrus.commands.channeladd.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/channeldel.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/channeldel.xml
+++ peardoc/en/pyrus/commands/channeldel.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.channeldel">
 <info><title>channel-del - remove a channel</title></info>

 <section xml:id="pyrus.commands.channeldel.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/channeldiscover.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/channeldiscover.xml
+++ peardoc/en/pyrus/commands/channeldiscover.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.channeldiscover">
 <info><title>channel-discover - add a channel by channel name</title></info>

 <section xml:id="pyrus.commands.channeldiscover.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/configshow.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/configshow.xml
+++ peardoc/en/pyrus/commands/configshow.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.configshow">
 <info><title>config-show - show all configuration values</title></info>

 <section xml:id="pyrus.commands.configshow.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/download.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/download.xml
+++ peardoc/en/pyrus/commands/download.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.download">
 <info><title>download - download a package</title></info>

 <section xml:id="pyrus.commands.download.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/help.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/help.xml
+++ peardoc/en/pyrus/commands/help.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.help">
 <info><title>help - list commands or get detailed help on a command</title></info>

 <section xml:id="pyrus.commands.help.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/info.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/info.xml
+++ peardoc/en/pyrus/commands/info.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.info">
 <info><title>info - get information on a package</title></info>

 <section xml:id="pyrus.commands.info.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/listchannels.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/listchannels.xml
+++ peardoc/en/pyrus/commands/listchannels.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.listchannels">
 <info><title>list-channels - list known channels</title></info>

 <section xml:id="pyrus.commands.listchannels.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/listpackages.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/listpackages.xml
+++ peardoc/en/pyrus/commands/listpackages.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.list-packages">
 <info><title>list-packages - list all installed packages in all channels</title></info>

 <section xml:id="pyrus.commands.listpackages.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/listupgrades.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/listupgrades.xml
+++ peardoc/en/pyrus/commands/listupgrades.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.listupgrades">
 <info><title>list-upgrades - list all available upgrades</title></info>

 <section xml:id="pyrus.commands.listupgrades.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/make.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/make.xml
+++ peardoc/en/pyrus/commands/make.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.make">
 <info><title>make - create a package.xml from its source directory</title></info>

 <section xml:id="pyrus.commands.make.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/mypear.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/mypear.xml
+++ peardoc/en/pyrus/commands/mypear.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.mypear">
 <info><title>mypear - set the pear path: location of PEAR installations to manage by default</title></info>

 <section xml:id="pyrus.commands.mypear.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/package.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/package.xml
+++ peardoc/en/pyrus/commands/package.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.package">
 <info><title>package - create a packaged release in phar, tar, tgz or zip format</title></info>

 <section xml:id="pyrus.commands.package.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/pickle.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/pickle.xml
+++ peardoc/en/pyrus/commands/pickle.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.pickle">
 <info><title>pickle - automatically create a PECL package.xml and package release from source directory</title></info>

 <section xml:id="pyrus.commands.pickle.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/remotelist.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/remotelist.xml
+++ peardoc/en/pyrus/commands/remotelist.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.remotelist">
 <info><title>remote-list - list remote packages on a channel</title></info>

 <section xml:id="pyrus.commands.remotelist.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/runphpt.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/runphpt.xml
+++ peardoc/en/pyrus/commands/runphpt.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.runphpt">
 <info><title>run-phpt - execute PHPT tests</title></info>

 <section xml:id="pyrus.commands.runphpt.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/runscripts.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/runscripts.xml
+++ peardoc/en/pyrus/commands/runscripts.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.runscripts">
 <info><title>run-scripts - execute post-install scripts for specified packages</title></info>

 <section xml:id="pyrus.commands.runscripts.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/set.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/set.xml
+++ peardoc/en/pyrus/commands/set.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.set">
 <info><title>set - set a configuration value</title></info>

 <section xml:id="pyrus.commands.set.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/uninstall.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/uninstall.xml
+++ peardoc/en/pyrus/commands/uninstall.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.uninstall">
 <info><title>uninstall - remove a package</title></info>

 <section xml:id="pyrus.commands.uninstall.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/upgrade.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/upgrade.xml
+++ peardoc/en/pyrus/commands/upgrade.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.upgrade">
 <info><title>upgrade - upgrade or install a package</title></info>

 <section xml:id="pyrus.commands.upgrade.intro">
  <info><title>Introduction</title></info>
  <para>
   The upgrade command is almost identical to the <link linkend="pyrus.commands.install">install</link>
   command.  The only difference is that upgrade will also upgrade an existing package
   as well as install a new one.
  </para>
 </section>
</section>

http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/upgraderegistry.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/upgraderegistry.xml
+++ peardoc/en/pyrus/commands/upgraderegistry.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.upgraderegistry">
 <info><title>upgrade-registry - convert a registry from PEAR format to Pyrus format</title></info>

 <section xml:id="pyrus.commands.upgraderegistry.intro">
  <info><title>Introduction</title></info>
  <para>This is a work in progress.</para>
 </section>
</section>