philip Sat Mar 3 23:01:09 2007 UTC
Modified files:
/phpdoc/en/install pecl.xml
Log:
Use the pecl command instead of the pear command.
Feel free to research the history. It appears 1.4.0 introduced pecl, and
made pear not install PECL extensions. They both use pearcmd.php currently.
The pear command gives a warning for PECL extensions so users shouldn't
be too confused without version information.
http://cvs.php.net/viewvc.cgi/phpdoc/en/install/pecl.xml?r1=1.14&r2=1.15&diff_format=u
Index: phpdoc/en/install/pecl.xml
diff -u phpdoc/en/install/pecl.xml:1.14 phpdoc/en/install/pecl.xml:1.15
--- phpdoc/en/install/pecl.xml:1.14 Sun Jan 28 17:26:57 2007
+++ phpdoc/en/install/pecl.xml Sat Mar 3 23:01:09 2007
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.14 $ -->
+<!-- $Revision: 1.15 $ -->
<chapter id="install.pecl">
<title>Installation of PECL extensions</title>
@@ -17,6 +17,8 @@
to the PHP source distribution, and that <literal>extname</literal> is the
name of the
PECL extension. Adjust accordingly. These instructions also assume a
familiarity with the <ulink url="&url.php.pear.cli;">pear command</ulink>.
+ The information in the PEAR manual for the <literal>pear</literal> command
also
+ applies to the <literal>pecl</literal> command.
</simpara>
<simpara>
To be useful, a shared extension must be built, installed, and loaded. The
@@ -58,7 +60,7 @@
<simpara>
PECL extensions that have releases listed on the PECL web site are
available for download and installation using the <ulink
- url="&url.php.pear.cli;">pear command</ulink>.
+ url="&url.php.pear.cli;">pecl command</ulink>.
Specific revisions may also be specified.
</simpara>
</listitem>
@@ -116,10 +118,10 @@
</sect1>
<sect1 id="install.pecl.pear">
- <title>Compiling shared PECL extensions with PEAR</title>
+ <title>Compiling shared PECL extensions with the pecl command</title>
<simpara>
- PEAR makes it easy to create shared PHP extensions. Using the
- <ulink url="&url.php.pear.cli;">pear command</ulink>, do the following:
+ PECL makes it easy to create shared PHP extensions. Using the
+ <ulink url="&url.php.pear.cli;">pecl command</ulink>, do the following:
</simpara>
<para>
<screen>
@@ -133,7 +135,7 @@
<filename>extname.so</filename> may then be loaded via &php.ini;
</simpara>
<simpara>
- By default, the <literal>pear</literal> command will not install
+ By default, the <literal>pecl</literal> command will not install
packages that are marked with the <literal>alpha</literal> or
<literal>beta</literal> state. If no <literal>stable</literal> packages
are available, you may install a <literal>beta</literal> package using the
@@ -157,9 +159,9 @@
<sect1 id="install.pecl.phpize">
<title>Compiling shared PECL extensions with phpize</title>
<simpara>
- Sometimes, using the <literal>pear</literal> installer is not an option.
+ Sometimes, using the <literal>pecl</literal> installer is not an option.
This could be because you're behind a firewall, or it could be because the
- extension you want to install is not available as a PEAR compatible
+ extension you want to install is not available as a PECL compatible
package, such as unreleased extensions from CVS. If you need to build such
an extension, you can use the lower-level build tools to perform the build
manually.
@@ -211,7 +213,7 @@
<screen>
<![CDATA[
$ cd /your/phpsrcdir/ext
-$ pear download extname
+$ pecl download extname
$ gzip -d < extname.tgz | tar -xvf -
$ mv extname-x.x.x extname
]]>
