cvs: peardoc / manual.xml /en language-defs.ent /en/channels whatarethey.xml /en/core rest.xml /en/guide/migrating channels.xml intro.xml /en/guide/migrating/channels xml.xml xmlrpcfunctions.xml /en/guide/users/commandline channels.xml /en/pyrus about.xml commands.xml differences.xml /en/pyrus/about whatis.xml /en/pyrus/commands install.xml
[email protected] ("Greg Beaver")
| Newsgroups | php.pear.doc |
|---|---|
| Message-ID | <cvscellog1245993721@cvsserver> |
cellog Fri Jun 26 05:22:01 2009 UTC
Added files:
/peardoc/en/channels whatarethey.xml
/peardoc/en/pyrus commands.xml differences.xml
/peardoc/en/pyrus/about whatis.xml
/peardoc/en/pyrus/commands install.xml
Removed files:
/peardoc/en/guide/migrating channels.xml
Modified files:
/peardoc manual.xml
/peardoc/en language-defs.ent
/peardoc/en/core rest.xml
/peardoc/en/guide/migrating intro.xml
/peardoc/en/guide/migrating/channels xml.xml xmlrpcfunctions.xml
/peardoc/en/guide/users/commandline channels.xml
/peardoc/en/pyrus about.xml
Log:
major re-organization: channels is now a top-level element, and begin better tweaks to pyrus docs
cellog-20090626052201.txt
(text/plain, 22 KB)
http://cvs.php.net/viewvc.cgi/peardoc/manual.xml?r1=1.7&r2=1.8&diff_format=u
Index: peardoc/manual.xml
diff -u peardoc/manual.xml:1.7 peardoc/manual.xml:1.8
--- peardoc/manual.xml:1.7 Thu Jun 18 04:50:40 2009
+++ peardoc/manual.xml Fri Jun 26 05:22:00 2009
@@ -71,6 +71,8 @@
<title>&Pyrus;</title>
&pyrus.about;
+ &pyrus.commands;
+ &pyrus.differences;
&pyrus.plugins;
&pyrus.developers;
</book>
@@ -122,13 +124,11 @@
<title>&Core;</title>
&core.pear;
&core.ppm;
- &core.rest;
</part>
<part xml:id="developers-changes14">
<title>&ChangesInPear14;</title>
&guide.migrating.intro;
- &guide.migrating.channels;
&guide.migrating.customroles;
&guide.migrating.customtasks;
&guide.migrating.postinstall;
@@ -137,6 +137,16 @@
&chapters.rfcs;
</book>
+ <book xml:id="channels">
+ <title>&Channels;</title>
+ &channels.whatarethey;
+ </book>
+
+<!-- This will soon be ready to go
+ <set xml:id="packages">
+ <title>&PEAR2Packages;</title>
+ </set>
+-->
<set xml:id="packages">
<title>&Packages;</title>
http://cvs.php.net/viewvc.cgi/peardoc/en/language-defs.ent?r1=1.11&r2=1.12&diff_format=u
Index: peardoc/en/language-defs.ent
diff -u peardoc/en/language-defs.ent:1.11 peardoc/en/language-defs.ent:1.12
--- peardoc/en/language-defs.ent:1.11 Thu Jun 18 04:50:40 2009
+++ peardoc/en/language-defs.ent Fri Jun 26 05:22:00 2009
@@ -1,18 +1,19 @@
-<!-- $Revision: 1.11 $ -->
+<!-- $Revision: 1.12 $ -->
<!ENTITY PEARManual "PEAR Manual">
<!ENTITY Translatedby "Translated by">
<!ENTITY Date "Date:">
<!ENTITY AboutPEAR "About PEAR and PEAR2">
<!ENTITY CodingStandards "Coding Standards">
-<!ENTITY Pyrus "Using Pyrus (PHP 5.3+)">
+<!ENTITY Pyrus "Using Pyrus, the PEAR Installer for PHP 5.3+">
<!ENTITY DevelopersGuide "PEAR Developer Guide">
+<!ENTITY Channels "Channels: distributing your packages">
<!ENTITY UsersGuide "User Guide">
<!ENTITY NewMaintainersGuide "Becoming a PEAR developer: how to get involved">
-<!ENTITY ChangesInPear14 "Channels, package.xml and customizing packages">
+<!ENTITY ChangesInPear14 "PEAR Installer: package.xml and customizing packages">
<!ENTITY Features "Features">
<!ENTITY PEAR "PEAR: the PHP Extension and Application Repository">
<!ENTITY PEAR2Packages "PEAR2 Packages">
<!ENTITY Packages "PEAR Packages">
-<!ENTITY Core "PEAR Installer: Core components (Installer API, REST, error handling)">
+<!ENTITY Core "PEAR Installer: Core components (Installer API, error handling)">
<!ENTITY Contributing "Contributing to PEAR">
http://cvs.php.net/viewvc.cgi/peardoc/en/core/rest.xml?r1=1.5&r2=1.6&diff_format=u
Index: peardoc/en/core/rest.xml
diff -u peardoc/en/core/rest.xml:1.5 peardoc/en/core/rest.xml:1.6
--- peardoc/en/core/rest.xml:1.5 Mon Nov 17 21:06:08 2008
+++ peardoc/en/core/rest.xml Fri Jun 26 05:22:00 2009
@@ -1,5 +1,7 @@
<?xml version="1.0" encoding="utf-8"?>
-<chapter xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="core.rest"><info><title>PEAR channel server REST interface</title></info>
+<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="core.rest">
+
+ <title>PEAR channel server REST interface</title>
@@ -9,8 +11,6 @@
formats look like.
</para>
- &blankpagehack;
-
&core.rest.directorystructure;
&core.rest.fileformats;
&core.rest.history;
@@ -35,4 +35,4 @@
<cweiske> but nothing more
-->
-</chapter>
+</section>
http://cvs.php.net/viewvc.cgi/peardoc/en/guide/migrating/intro.xml?r1=1.3&r2=1.4&diff_format=u
Index: peardoc/en/guide/migrating/intro.xml
diff -u peardoc/en/guide/migrating/intro.xml:1.3 peardoc/en/guide/migrating/intro.xml:1.4
--- peardoc/en/guide/migrating/intro.xml:1.3 Thu Oct 9 15:16:18 2008
+++ peardoc/en/guide/migrating/intro.xml Fri Jun 26 05:22:00 2009
@@ -2,27 +2,12 @@
<chapter xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="guide.migrating.intro">
<info><title>Introduction</title>
<author><personname><firstname>Gregory</firstname><surname>Beaver</surname></personname></author>
- <date>$Date: 2008/10/09 15:16:18 $</date>
+ <date>$Date: 2009/06/26 05:22:00 $</date>
</info>
-
<simpara>
- The debut of PEAR 1.4.0 is very exciting. This chapter documents all of the differences
- between PEAR 1.3.x and the new features introduced in PEAR 1.4.
- </simpara>
-
- <simpara>
- The most significant change in PEAR 1.4 is the addition of
- <link linkend="guide.migrating.channels">channels</link>, a simple and
- effective method of distributing application development. This change has
- driven most of the other changes to PEAR, and in fact full application support
- is a major goal of this release.
- </simpara>
-
- <simpara>
- In addition to channels, support for customization of the install process has been
- seriously enhanced with the addition of three essential features for application
- development:
+ Extending the PEAR Installer is made possible through custom file roles, file tasks,
+ post-installation scripts and custom commands.
</simpara>
<para>
http://cvs.php.net/viewvc.cgi/peardoc/en/guide/migrating/channels/xml.xml?r1=1.5&r2=1.6&diff_format=u
Index: peardoc/en/guide/migrating/channels/xml.xml
diff -u peardoc/en/guide/migrating/channels/xml.xml:1.5 peardoc/en/guide/migrating/channels/xml.xml:1.6
--- peardoc/en/guide/migrating/channels/xml.xml:1.5 Thu Oct 9 15:16:18 2008
+++ peardoc/en/guide/migrating/channels/xml.xml Fri Jun 26 05:22:00 2009
@@ -1,10 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
-<refentry xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="guide.migrating.channels.xml">
- <refnamediv>
- <refname>channel.xml</refname>
- <refpurpose>The channel definition file</refpurpose>
- </refnamediv>
- <refsection xml:id="guide.migrating.channels.xml.intro"><info><title>How to describe a channel</title></info>
+<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="guide.migrating.channels.xml">
+ <title>channel.xml: The channel definition file</title>
+ <section xml:id="guide.migrating.channels.xml.intro">
+ <title>How to describe a channel</title>
<para>
Discovery of a channel's capabilities is extremely flexible. The XSD schema
@@ -98,7 +96,7 @@
</channel>
</programlisting>
</para>
- <refsection xml:id="guide.migrating.channels.xml.name"><info><title><name></title></info>
+ <section xml:id="guide.migrating.channels.xml.name"><title><name></title>
<para>
A channel's name should be the name of the server that users would browse to in order
@@ -135,8 +133,8 @@
"pear.example.com/path/to/pear", then the channel.xml must be located in
"http://pear.example.com/path/to/pear/channel.xml"
</para>
- </refsection>
- <refsection xml:id="guide.migrating.channels.xml.suggestedalias"><info><title><suggestedalias></title></info>
+ </section>
+ <section xml:id="guide.migrating.channels.xml.suggestedalias"><title><suggestedalias></title>
<para>
<suggestedalias> defines a shorter, more friendly name to use when installing
@@ -151,16 +149,16 @@
the user does not like the alias suggested by the channel owners, he or she can
easily re-alias a channel through the channel-alias command.
</para>
- </refsection>
- <refsection xml:id="guide.migrating.channels.xml.summary"><info><title><summary></title></info>
+ </section>
+ <section xml:id="guide.migrating.channels.xml.summary"><title><summary></title>
<para>
This tag provides a short description of what packages the user should expect to
find on this channel. The summary is what users will see when the use the list-channels
command.
</para>
- </refsection>
- <refsection xml:id="guide.migrating.channels.xml.validatepackage"><info><title><validatepackage></title></info>
+ </section>
+ <section xml:id="guide.migrating.channels.xml.validatepackage"><title><validatepackage></title>
<para>
Most channels will be satisfied with the restrictions placed upon package naming,
@@ -204,8 +202,8 @@
<function>validateVersion</function> are intended to be overridden by validation classes
for use in extending existing validation functionality.
</para>
- </refsection>
- <refsection xml:id="guide.migrating.channels.xml.mirrors"><info><title><servers>: <primary> and <mirror></title></info>
+ </section>
+ <section xml:id="guide.migrating.channels.xml.mirrors"><title><servers>: <primary> and <mirror></title>
<para>
Mirroring is explicitly supported in channel.xml and in the PEAR installer. Users can
@@ -221,8 +219,8 @@
to XML-RPC and SOAP services. REST services are always controlled by the individual
<baseurl> tags.
</para>
- </refsection>
- <refsection xml:id="guide.migrating.channels.xml.protocols"><info><title><xmlrpc>, <soap>, <rest></title></info>
+ </section>
+ <section xml:id="guide.migrating.channels.xml.protocols"><title><xmlrpc>, <soap>, <rest></title>
<para>
channel.xml knows about the XML-RPC, SOAP, and REST protocols for web services.
@@ -247,7 +245,7 @@
provide. Required attribute "type" tells the installer what version of
the PEAR installer REST interface is provided at the base URL.
</para>
- <refsection xml:id="guide.migrating.channels.xml.protocols.function"><info><title><function></title></info>
+ <section xml:id="guide.migrating.channels.xml.protocols.function"><title><function></title>
<para>
The <function> tag is quite simple. A required version attribute informs the
@@ -263,9 +261,9 @@
If a newer API is backwards-compatible, always define every possible API version
in order to prevent older installer versions from giving up.
</para>
- </refsection>
- </refsection>
- <refsection xml:id="guide.migrating.channels.xml.whynotwsdl"><info><title>Why not use a standard such as wsdl?</title></info>
+ </section>
+ </section>
+ <section xml:id="guide.migrating.channels.xml.whynotwsdl"><title>Why not use a standard such as wsdl?</title>
<para>
Some of you may be asking "why create another standard for web
@@ -280,6 +278,6 @@
function package.info version 1.0 requires and what it returns. Any other information
simply adds wasted bandwidth and disk space.
</para>
- </refsection>
- </refsection>
-</refentry>
+ </section>
+ </section>
+</section>
http://cvs.php.net/viewvc.cgi/peardoc/en/guide/migrating/channels/xmlrpcfunctions.xml?r1=1.9&r2=1.10&diff_format=u
Index: peardoc/en/guide/migrating/channels/xmlrpcfunctions.xml
diff -u peardoc/en/guide/migrating/channels/xmlrpcfunctions.xml:1.9 peardoc/en/guide/migrating/channels/xmlrpcfunctions.xml:1.10
--- peardoc/en/guide/migrating/channels/xmlrpcfunctions.xml:1.9 Wed Feb 25 13:29:23 2009
+++ peardoc/en/guide/migrating/channels/xmlrpcfunctions.xml Fri Jun 26 05:22:00 2009
@@ -1,10 +1,8 @@
<?xml version="1.0" encoding="utf-8"?>
-<refentry xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="guide.migrating.channels.xmlrpcfunctions">
- <refnamediv>
- <refname>XML-RPC functions</refname>
- <refpurpose>XML-RPC function API documentation</refpurpose>
- </refnamediv>
- <refsection xml:id="guide.migrating.channels.xmlrpcfunctions.intro"><info><title>What XML-RPC functions are available in a standard channel?</title></info>
+<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="guide.migrating.channels.xmlrpcfunctions">
+ <title>(deprecated) XML-RPC functions</title>
+ <section xml:id="guide.migrating.channels.xmlrpcfunctions.intro">
+ <title>What XML-RPC functions are available in a standard channel?</title>
<para>
A standard PEAR channel should support this list of XML-RPC functions:
@@ -60,15 +58,15 @@
by pear.php.net and pecl.php.net channels, as the command is utilized by the update-channels
command to retrieve an official list of channels.
</para>
- </refsection>
- <refsection xml:id="guide.migrating.channels.xmlrpcfunctions.logintest"><info><title>logintest</title></info>
+ </section>
+ <section xml:id="guide.migrating.channels.xmlrpcfunctions.logintest"><title>logintest</title>
<para>
The logintest xml-rpc function is called by the login command, and should return a boolean
&true;
</para>
- </refsection>
- <refsection xml:id="guide.migrating.channels.xmlrpcfunctions.getdownloadurl"><info><title>package.getDownloadURL</title></info>
+ </section>
+ <section xml:id="guide.migrating.channels.xmlrpcfunctions.getdownloadurl"><title>package.getDownloadURL</title>
<para>
<funcsynopsis>
@@ -167,8 +165,8 @@
parameter. Version 1.1 of package.getDownloadURL does - that is the only difference
between the two versions.
</para>
- </refsection>
- <refsection xml:id="guide.migrating.channels.xmlrpcfunctions.getdepdownloadurl"><info><title>package.getDepDownloadURL</title></info>
+ </section>
+ <section xml:id="guide.migrating.channels.xmlrpcfunctions.getdepdownloadurl"><title>package.getDepDownloadURL</title>
<para>
<funcsynopsis>
@@ -322,8 +320,8 @@
parameter. Version 1.1 of package.getDepDownloadURL does - that is the only difference
between the two versions.
</para>
- </refsection>
- <refsection xml:id="guide.migrating.channels.xmlrpcfunctions.info"><info><title>package.info</title></info>
+ </section>
+ <section xml:id="guide.migrating.channels.xmlrpcfunctions.info"><title>package.info</title>
<para>
<funcsynopsis>
@@ -466,8 +464,8 @@
</varlistentry>
</variablelist>
</para>
- </refsection>
- <refsection xml:id="guide.migrating.channels.xmlrpcfunctions.listall"><info><title>package.listAll</title></info>
+ </section>
+ <section xml:id="guide.migrating.channels.xmlrpcfunctions.listall"><title>package.listAll</title>
<para>
<funcsynopsis>
@@ -532,8 +530,8 @@
]]>
</programlisting>
</para>
- </refsection>
- <refsection xml:id="guide.migrating.channels.xmlrpcfunctions.listlatestreleases"><info><title>package.listLatestReleases</title></info>
+ </section>
+ <section xml:id="guide.migrating.channels.xmlrpcfunctions.listlatestreleases"><title>package.listLatestReleases</title>
<para>
<funcsynopsis>
@@ -583,8 +581,8 @@
]]>
</programlisting>
</para>
- </refsection>
- <refsection xml:id="guide.migrating.channels.xmlrpcfunctions.search"><info><title>package.search</title></info>
+ </section>
+ <section xml:id="guide.migrating.channels.xmlrpcfunctions.search"><title>package.search</title>
<para>
<funcsynopsis>
@@ -674,5 +672,5 @@
]]>
</programlisting>
</para>
- </refsection>
-</refentry>
+ </section>
+</section>
http://cvs.php.net/viewvc.cgi/peardoc/en/guide/users/commandline/channels.xml?r1=1.3&r2=1.4&diff_format=u
Index: peardoc/en/guide/users/commandline/channels.xml
diff -u peardoc/en/guide/users/commandline/channels.xml:1.3 peardoc/en/guide/users/commandline/channels.xml:1.4
--- peardoc/en/guide/users/commandline/channels.xml:1.3 Thu Oct 9 15:16:18 2008
+++ peardoc/en/guide/users/commandline/channels.xml Fri Jun 26 05:22:01 2009
@@ -5,7 +5,7 @@
<section xml:id="guide.users.commandline.channels.channels"><info><title>Channels?</title></info>
- <para>Channels are alternative package sources. See the <link linkend="guide.migrating.channels">channel section</link> of the manual
+ <para>Channels are alternative package sources. See the <link linkend="channels.whatarethey">channel section</link> of the manual
for more information.</para>
<para>What you need to know now: By using channels, you can install
http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/about.xml?r1=1.2&r2=1.3&diff_format=u
Index: peardoc/en/pyrus/about.xml
diff -u peardoc/en/pyrus/about.xml:1.2 peardoc/en/pyrus/about.xml:1.3
--- peardoc/en/pyrus/about.xml:1.2 Fri Jun 26 03:25:48 2009
+++ peardoc/en/pyrus/about.xml Fri Jun 26 05:22:01 2009
@@ -1,18 +1,26 @@
<?xml version="1.0" encoding="utf-8"?>
<chapter xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.about">
<info>
- <title>Pyrus</title>
+ <title>About Pyrus</title>
<author><personname><firstname>Gregory</firstname><surname>Beaver</surname></personname></author>
<date>2009-06-16</date>
</info>
- <simpara>
- About Pyrus, the PEAR Installer for PHP 5.3+. This documentation is a work in progress.
- </simpara>
+ <para>
+ This documentation is organized
+ with progressive complexity in mind. If you are new to Pyrus, then you should
+ start with the <link linkend="pyrus.commands">Pyrus commands</link> section
+ to familiarize yourself with the commands available for users of Pyrus.
+ </para>
+ <para>
+ If you are migrating from using the PEAR installer, it will be helpful to
+ read the section on <link linkend="pyrus.differences.frompear">differences
+ from PEAR</link>.
+ </para>
+ <para>
+ If you wish to extend Pyrus, read the section on <link
+ linkend="pyrus.plugins">plugins</link>.
+ </para>
- &pyrus.differences.frompear;
- &pyrus.differences.postinstallscripts;
- &pyrus.differences.customcommands;
- &pyrus.differences.customroles;
- &pyrus.differences.customtasks;
+ &pyrus.about.whatis;
</chapter>
http://cvs.php.net/viewvc.cgi/peardoc/en/channels/whatarethey.xml?view=markup&rev=1.1
Index: peardoc/en/channels/whatarethey.xml
+++ peardoc/en/channels/whatarethey.xml
<?xml version="1.0" encoding="utf-8"?>
<chapter xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="channels.whatarethey">
<info>
<title>channel.xml, REST, XML-RPC</title>
<author><personname><firstname>Gregory</firstname><surname>Beaver</surname></personname></author>
<date>2009-06-25</date>
</info>
<para>
What is a PEAR Channel? PEAR Channels make it possible to take advantage of
the strengths of the PEAR Installer and Pyrus for your own personal packages.
A channel is simply a website that provides packages for download and a few
extra meta-information files.
</para>
<para>
A familiar example of a channel is
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://pear.php.net">pear.php.net</link>.
This channel was the first channel, and defines the standards to which other
channels must adhere. Each channel has a <link linkend="guide.migrating.channels.xml">channel.xml</link>
file in its document root (such as <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://pear.php.net/channel.xml">
http://pear.php.net/channel.xml</link>) and a series of files utilizing the
<literal>REST</literal> (Representational State Transfer) paradigm to describe
the packages available for installation and download. The <literal>pear.php.net</literal>
channel's <literal>REST</literal> files can be viewed at <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://pear.php.net/rest">
http://pear.php.net/rest</link>.
</para>
&guide.migrating.channels.xml;
&core.rest;
&guide.migrating.channels.xmlrpcfunctions;
</chapter>
http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands.xml
+++ peardoc/en/pyrus/commands.xml
<?xml version="1.0" encoding="utf-8"?>
<chapter xmlns="http://docbook.org/ns/docbook" 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>
<simpara>
Commands available for Pyrus. This documentation is a work in progress.
</simpara>
&pyrus.commands.install;
</chapter>
http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/differences.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/differences.xml
+++ peardoc/en/pyrus/differences.xml
<?xml version="1.0" encoding="utf-8"?>
<chapter xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.differences">
<info>
<title>Differences from the PEAR Installer</title>
<author><personname><firstname>Gregory</firstname><surname>Beaver</surname></personname></author>
<date>2009-06-25</date>
</info>
<simpara>
Differences between Pyrus and the PEAR Installer. This documentation is a work in progress.
</simpara>
&pyrus.differences.frompear;
&pyrus.differences.postinstallscripts;
&pyrus.differences.customcommands;
&pyrus.differences.customroles;
&pyrus.differences.customtasks;
</chapter>
http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/about/whatis.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/about/whatis.xml
+++ peardoc/en/pyrus/about/whatis.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.about.whatis">
<info><title>What is a "Pyrus"?</title></info>
<section xml:id="pyrus.about.whatis.intro">
<info><title>Pyrus</title></info>
<para>
In botany (the science of plants), <literal>Pyrus</literal> is the genus of
the pear family, and thus includes all of the pear-producing trees and
shrubs under its taxonomical umbrella.
</para>
<para>
In PHP (the hypertext programming language), <literal>Pyrus</literal> is
the next-generation PEAR Installer, a revolutionary package management
and distribution system that extends the functionality of the PEAR Installer's
already advanced functionality. Pyrus is also friendlier to projects
outside of PEAR that wish to take advantage of the strengths of PEAR through
<link linkend="channels">channels</link>.
</para>
<para>
This documentation is a work in progress.
</para>
</section>
</section>
http://cvs.php.net/viewvc.cgi/peardoc/en/pyrus/commands/install.xml?view=markup&rev=1.1
Index: peardoc/en/pyrus/commands/install.xml
+++ peardoc/en/pyrus/commands/install.xml
<?xml version="1.0" encoding="utf-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="pyrus.commands.install">
<info><title>install - install a package</title></info>
<section xml:id="pyrus.commands.install.intro">
<info><title>Introduction</title></info>
<para>This is a work in progress.</para>
</section>
</section>