cvs: peardoc /en/chapters/faq users.xml
[email protected] ("Alexander Merz")
| Newsgroups | php.pear.doc |
|---|---|
| Message-ID | <cvsalexmerz1196826277@cvsserver> |
alexmerz Wed Dec 5 03:44:37 2007 UTC
Modified files:
/peardoc/en/chapters/faq users.xml
Log:
nice typo
alexmerz-20071205034437.txt
(text/plain, 29.2 KB)
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/faq/users.xml?r1=1.7&r2=1.8&diff_format=u
Index: peardoc/en/chapters/faq/users.xml
diff -u peardoc/en/chapters/faq/users.xml:1.7 peardoc/en/chapters/faq/users.xml:1.8
--- peardoc/en/chapters/faq/users.xml:1.7 Sun Dec 2 04:18:11 2007
+++ peardoc/en/chapters/faq/users.xml Wed Dec 5 03:44:37 2007
@@ -1,414 +1,414 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- $Revision: 1.7 $ -->
-<sect1 id="faq.users">
- <title>User FAQ</title>
-
- <sect2 id="faq.whatis">
- <title>
- What is PEAR?
- </title>
- <para>
- This is described <link linkend="introduction">here</link>.
- </para>
- </sect2>
-
-
- <sect2 id="faq.noreleasesfound">
- <title>
- How do I install a package when I get the error message
- "No release with state equal to: 'stable' found for 'Packagename'"?
- </title>
- <titleabbrev>
- No release with state equal to: 'stable' found for 'Packagename'
- </titleabbrev>
- <simpara>
- answer by Greg Beaver
- </simpara>
- <para>
- The package in question does have releases, but none that are stable.
- There are two solutions.
- </para>
- <para>
- <orderedlist>
- <listitem>
- <para>
- Set preferred_state to alpha or beta and then install
- </para>
- <para>
- <command>$ pear config-set preferred_state alpha</command>
- </para>
- <para>
- <command>$ pear install Packagename</command>
- </para>
- </listitem>
- <listitem>
- <para>
- Find out the stability or version number of the latest release and install it directly.
- </para>
- <para>
- <command>$ pear install Packagename-alpha</command>
- </para>
- <para>
- <command>$ pear install Packagename-1.5.3</command>
- </para>
- </listitem>
- </orderedlist>
- </para>
- </sect2>
-
-
- <sect2 id="faq.no-handlers">
- <title>
- Why do I get "No handlers for package.xml version 2.0" when I try to
- install a package?
- </title>
- <titleabbrev>
- No handlers for package.xml version 2.0
- </titleabbrev>
- <para>
- You are using a PEAR version lower than 1.4.0.
- </para>
- <para>
- To install the package, you have to update PEAR via:
- </para>
- <para>
- <command>$ pear upgrade PEAR</command>
- </para>
- <para>
- This will install the latest available version of PEAR which is capable of
- installing packages that have only a package.xml version 2.0.
- </para>
- <para>
- If you have an old PEAR version installed (i.e. < 1.3.6), you need to
- use the following two commands to install the latest available version of
- PEAR:
- </para>
- <para>
- <command>$ pear upgrade -a PEAR-1.3.6</command>
- </para>
- <para>
- <command>$ pear upgrade -a PEAR</command>
- </para>
- </sect2>
-
-
- <sect2 id="faq.no-documentation">
- <title>
- There is no end-user documentation for this package!
- How am I supposed to know how it works?
- </title>
- <titleabbrev>
- No package documentation
- </titleabbrev>
- <para>
- Even if not all packages do have end-user documentation in
- the PEAR manual, nearly all of the packages do include
- examples. The examples are automatically installed when
- you install a package via the command line installer and
- are located in <filename>$peardir/docs/$packagename/</filename>.
- </para>
- <para>
- You can find the example/documentation directory by executing
- <command>$ pear config-get doc_dir</command> on command line.
- </para>
- </sect2>
-
-
- <sect2 id="faq.question">
- <title>
- I have a question about PEAR. Where should I ask?
- </title>
- <titleabbrev>
- Asking questions
- </titleabbrev>
- <para>
- <itemizedlist>
- <listitem>
- <para>
- General questions about the usage of PEAR components
- should be posted to the mailing list
- <ulink url="mailto:&email.pear.general;">&email.pear.general;</ulink>.
- </para>
- </listitem>
- <listitem>
- <para>
- All technical discussions concerning the development of PEAR
- components should be posted to <ulink url="mailto:&email.pear.dev;">
- &email.pear.dev;</ulink>.
- </para>
- </listitem>
- <listitem>
- <para>
- Question concerning the website can be sent to
- <ulink url="mailto:&email.pear.webmaster;">
- &email.pear.webmaster;</ulink>.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- <para>
- Information on subscribing this mailing lists can be found
- <ulink url="&url.pear.support;">here</ulink>.
- </para>
- <para>
- On all mailing lists mentioned above the language is english and
- the way you ask questions should always be polite :-).
- </para>
- </sect2>
-
- <sect2 id="faq.macosx">
- <title>
- Does PEAR work on Mac OS X?
- </title>
- <titleabbrev>
- PEAR & Max OS X
- </titleabbrev>
- <simpara>
- answer by Brett Bieber
- </simpara>
- <para>
- All Mac OS X versions up until 10.5 come with PEAR by default. Mac OS X 10.5
- (Leopard) users will need to install PEAR using the standard installation
- instructions.
- </para>
- <para>
- If you are a OS X 10.4 or lower user, you may wish to upgrade to a newer version
- of PHP using a binary installable package such as Marc Liyanage's PHP packages.
- If you have installed another PHP package, you may have two versions of PHP and
- PEAR installed on your system. To be sure which version you are using, type
- <command>which pear</command> in your console to find out where PEAR is
- located, and <command>pear -V</command> to find out some info about the pear
- version, and also <command>pear config-show</command> to see the configuration
- details.
- </para>
- <para>
- If you have not made any modifications to the default Max OS X install, the PEAR
- version you are running is the <filename>/usr/bin/pear</filename> which is
- configured for the PHP 4 version distributed with OS X. If this is the case,
- there are a couple options.
- </para>
- <para>
- If you're using Marc Liyanage's PHP package, you might want to specify
- <command>/usr/local/php5/bin/pear install {packagename}</command> (will probably
- require sudo to install/upgrade packages), and always specify the full path when
- you run pear & php through the console.
- </para>
- <para>
- Or you could change every path for the OS X provided PEAR using config-set,
- or, what I do is <command>sudo rm /usr/bin/php /usr/bin/pear</command> and then
- <command>sudo ln -s /usr/local/php5/bin/php /usr/bin/php</command>
- <command>sudo ln -s /usr/local/php5/bin/pear /usr/bin/pear</command> - which
- will remove the PHP 4 version and link it to Marc Liyanage's PHP 5 version.
- Keep in mind, Apple occasionally updates PHP on OSX, which will revert your
- <filename>/usr/bin/php</filename> to their distributed version.
- </para>
- <simpara>
- Note: It is uncertain if Apple will continue to distribute PHP version 4 for
- Mac OS X <= 10.4. So these instructions may change, and may differ for your
- specific version of Mac OS X. Always consult the Apple documentation to
- understand the default install provided before making modifications.
- </simpara>
- </sect2>
-
- <sect2 id="faq.windows">
- <title>
- Does PEAR work on windows?
- </title>
- <titleabbrev>
- PEAR & Windows
- </titleabbrev>
- <para>
- To make PEAR work on Windows, you simple need to add the PEAR
- installation dir (e.g. <filename>c:\php\pear</filename>) to the
- include_path directive in your <filename>php.ini</filename>.
- </para>
- <simpara>
- Note: There are some classes (like Schedule/At.php), that do not
- work on Windows, because they use *nix specific commands.
- </simpara>
- </sect2>
-
-
- <sect2 id="faq.windows-build-out-of-date">
- <title>
- go-pear.php or bundled packages in the windows build of PHP 4.3.x is out of date!
- </title>
- <titleabbrev>
- PHP 4.3.x pear bundle out of date
- </titleabbrev>
- <para>
- Unlike other aspects of PEAR development, the windows build of PHP 4.3.x is not tracked
- in CVS. Instead, it is located on the machine that builds windows snapshots. Often,
- this will not be updated when the rest of PEAR is updated. Note that PHP 5.x releases
- use a different build system and are automatically updated to the latest versions of
- PEAR.
- </para>
- <para>
- If you find that PHP 4.3.x has out-of-date versions of packages, or no longer works, then
- please report that the windows bundle of PEAR is out of date to &email.pear.dev;
- </para>
- </sect2>
-
-
- <sect2 id="faq.ssl-certificate">
- <title>
- Why does my browser show strange warnings when logging in to the website?
- </title>
- <titleabbrev>
- SSL Certificate
- </titleabbrev>
- <para>
- You are seeing the warnings because <literal>pear.php.net</literal>
- uses a SSL key that is signed by <ulink url="&url.cacert;">CAcert</ulink>,
- whose root certificate is unfortunately not bundled with most
- browsers.
- </para>
- <para>
- If you are using a Mozilla browser, you can import the certificate
- <ulink url="&url.cacert.mozilla;">on this site</ulink> by clicking
- on the link <quote>Root Certificate (PEM Format)</quote>. When
- asked if you want to trust the new Certificate Authority, you need
- to check at least the <quote>Trust this CA to identify web sites.</quote>
- box and click "Ok".
- </para>
- <para>
- People using Internet Explorer may find help <ulink url="&url.cacert.ie;">here</ulink>.
- </para>
- <para>
- Mac OS X users must download the above mentioned PEM file. The
- certificate can then be imported with the <quote>Keychain Access</quote>
- utility via <quote>Import</quote> in the <quote>File</quote> menu.
- </para>
- </sect2>
-
-
- <sect2 id="faq.read-only-folders-windows">
- <title>
- Installing into customized windows folders fails
- </title>
- <titleabbrev>
- read-only isn't really read-only for customized windows folders
- </titleabbrev>
- <para>
- To know that the folder has a customized view, Windows sets the
- "read-only" attribute to the folder. The
- "read-only" attribute is not actually used to control write
- access. You can create files in a "read-only" folder.
- <ulink url="http://support.microsoft.com/default.aspx?scid=kb;en-us;326549">
- http://support.microsoft.com/default.aspx?scid=kb;en-us;326549</ulink>
- </para>
- <para>
- The PEAR Installer detects the read-only attribute and refuses to install
- into these folders. Unfortunately, there is no way to distinguish between
- customized folders and actual read-only folders on Windows.
- </para>
- <para>
- The work-around is to avoid installing PEAR packages into customized
- Windows folders.
- </para>
- </sect2>
-
-
- <sect2 id="faq.pearinhomedir">
- <title>
- I've got an old installation of PEAR and don't have the permissions to install a new version - what now?
- </title>
- <titleabbrev>
- Installing PEAR in your home directory
- </titleabbrev>
- <para>
- If <command>$ which pear</command> gives you something like <filename>/usr/local/bin/pear</filename>
- and <command>$ pear -V</command> shows a very old version or if you don't want
- to use it for other reasons, you have to install PEAR in your home directory.
- </para>
- <para>
- Go to &url.pear.go;, save as <filename>gopear.php</filename> and do
- <command>$ php gopear.php</command> or try
- <command>$ lynx -source &url.pear.go; | php -q</command>.
- </para>
- <para>
- Use <filename>/home/user/pear</filename> as prefix while installing PEAR, where user is your
- username.
- </para>
- <para>
- Once the installation is done, edit your PATH variable to include your planned new PEAR directory
- <emphasis>before</emphasis> the old one.
- </para>
- <para>
- For example put a <command>export PATH=/home/user/pear/bin:$PATH</command>
- at the end of your <filename>~/.bashrc</filename> or <filename>~/.profile</filename>
- under Linux. <command>$ echo $PATH</command> should give you now
- <filename>/home/user/pear/bin:[...]</filename>
- </para>
- <para>
- <command>$ which pear</command> should result in <filename>/home/user/pear/bin/pear</filename>
- and <command>$ pear -V</command> something like "PEAR Version: 1.4.8"
- (at the time of writing) or newer. Check the latest stable version at
- &url.pear.package;PEAR under <emphasis>Current Release</emphasis>.
- </para>
- <para>
- Now all you need is to set your <emphasis>include_path</emphasis> correctly, most
- likely via
- <programlisting role="php">
- <![CDATA[
- <?php
- $path = ini_get('include_path');
- ini_set('include_path', '/home/user/pear'.PATH_SEPARATOR.$path);
- ?>
- ]]>
- </programlisting>
- </para>
- </sect2>
-
- <sect2 id="faq.includepathproblems">
- <title>
- I have updated package X to get rid of errors like "undefined function Y",
- but PHP still shows the error message(s). What's wrong?
- </title>
- <titleabbrev>
- Errors still occur after package update
- </titleabbrev>
- <para>
- It is very likely that you have defined two PEAR directories in your
- <emphasis>include_path</emphasis>, and that you have updated the package
- in the directory that is defined behind the first directory in your
- <emphasis>include_path</emphasis>. If you either remove the wrong directory
- from your <emphasis>include_path</emphasis> or change the order of the
- directories in your <emphasis>include_path</emphasis>, the error messages
- should not be shown anymore.
- </para>
- </sect2>
-
- <sect2 id="faq.gopearnotparsed">
- <title>
- The downloaded go-pear.php isn't parsed by PHP! Why?
- </title>
- <titleabbrev>
- Downloaded go-pear.php isn't parsed
- </titleabbrev>
- <para>
- If you have followed <link linkend="installation.getting">the instructions
- for getting go-pear.php</link> and you are using e.g. Windows and the
- Internet Explorer, you might get the strange effect that -- although you
- have named the file go-pear.php -- the file isn't parsed and the PHP source
- code of it is shown.
- </para>
- <para>
- The problem is that e.g. the Internet Explorer saves the file as a HTML
- file with some HTML code around the PHP source code to display the code
- nicely.
- </para>
- <para>
- To avoid this problem, you should use the source code view of your browser,
- e.g. by clicking with the right mouse key and selecting "Show source code"
- from the context menu. If you save now the file that is shown in your
- editor as go-pear.php, PHP will be able to parse the file properly.
- </para>
- <para>
- Please note that the Windows versions of PHP have a file named <link
- linkend="installation.getting">go-pear.bat</link> bundled. It is recommended
- to use this batch file on Windows instead of using go-pear.php.
- </para>
- </sect2>
-
+<?xml version="1.0" encoding="utf-8"?>
+<!-- $Revision: 1.8 $ -->
+<sect1 id="faq.users">
+ <title>User FAQ</title>
+
+ <sect2 id="faq.whatis">
+ <title>
+ What is PEAR?
+ </title>
+ <para>
+ This is described <link linkend="introduction">here</link>.
+ </para>
+ </sect2>
+
+
+ <sect2 id="faq.noreleasesfound">
+ <title>
+ How do I install a package when I get the error message
+ "No release with state equal to: 'stable' found for 'Packagename'"?
+ </title>
+ <titleabbrev>
+ No release with state equal to: 'stable' found for 'Packagename'
+ </titleabbrev>
+ <simpara>
+ answer by Greg Beaver
+ </simpara>
+ <para>
+ The package in question does have releases, but none that are stable.
+ There are two solutions.
+ </para>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Set preferred_state to alpha or beta and then install
+ </para>
+ <para>
+ <command>$ pear config-set preferred_state alpha</command>
+ </para>
+ <para>
+ <command>$ pear install Packagename</command>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Find out the stability or version number of the latest release and install it directly.
+ </para>
+ <para>
+ <command>$ pear install Packagename-alpha</command>
+ </para>
+ <para>
+ <command>$ pear install Packagename-1.5.3</command>
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ </sect2>
+
+
+ <sect2 id="faq.no-handlers">
+ <title>
+ Why do I get "No handlers for package.xml version 2.0" when I try to
+ install a package?
+ </title>
+ <titleabbrev>
+ No handlers for package.xml version 2.0
+ </titleabbrev>
+ <para>
+ You are using a PEAR version lower than 1.4.0.
+ </para>
+ <para>
+ To install the package, you have to update PEAR via:
+ </para>
+ <para>
+ <command>$ pear upgrade PEAR</command>
+ </para>
+ <para>
+ This will install the latest available version of PEAR which is capable of
+ installing packages that have only a package.xml version 2.0.
+ </para>
+ <para>
+ If you have an old PEAR version installed (i.e. < 1.3.6), you need to
+ use the following two commands to install the latest available version of
+ PEAR:
+ </para>
+ <para>
+ <command>$ pear upgrade -a PEAR-1.3.6</command>
+ </para>
+ <para>
+ <command>$ pear upgrade -a PEAR</command>
+ </para>
+ </sect2>
+
+
+ <sect2 id="faq.no-documentation">
+ <title>
+ There is no end-user documentation for this package!
+ How am I supposed to know how it works?
+ </title>
+ <titleabbrev>
+ No package documentation
+ </titleabbrev>
+ <para>
+ Even if not all packages do have end-user documentation in
+ the PEAR manual, nearly all of the packages do include
+ examples. The examples are automatically installed when
+ you install a package via the command line installer and
+ are located in <filename>$peardir/docs/$packagename/</filename>.
+ </para>
+ <para>
+ You can find the example/documentation directory by executing
+ <command>$ pear config-get doc_dir</command> on command line.
+ </para>
+ </sect2>
+
+
+ <sect2 id="faq.question">
+ <title>
+ I have a question about PEAR. Where should I ask?
+ </title>
+ <titleabbrev>
+ Asking questions
+ </titleabbrev>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ General questions about the usage of PEAR components
+ should be posted to the mailing list
+ <ulink url="mailto:&email.pear.general;">&email.pear.general;</ulink>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ All technical discussions concerning the development of PEAR
+ components should be posted to <ulink url="mailto:&email.pear.dev;">
+ &email.pear.dev;</ulink>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Question concerning the website can be sent to
+ <ulink url="mailto:&email.pear.webmaster;">
+ &email.pear.webmaster;</ulink>.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ Information on subscribing this mailing lists can be found
+ <ulink url="&url.pear.support;">here</ulink>.
+ </para>
+ <para>
+ On all mailing lists mentioned above the language is english and
+ the way you ask questions should always be polite :-).
+ </para>
+ </sect2>
+
+ <sect2 id="faq.macosx">
+ <title>
+ Does PEAR work on Mac OS X?
+ </title>
+ <titleabbrev>
+ PEAR & Mac OS X
+ </titleabbrev>
+ <simpara>
+ answer by Brett Bieber
+ </simpara>
+ <para>
+ All Mac OS X versions up until 10.5 come with PEAR by default. Mac OS X 10.5
+ (Leopard) users will need to install PEAR using the standard installation
+ instructions.
+ </para>
+ <para>
+ If you are a OS X 10.4 or lower user, you may wish to upgrade to a newer version
+ of PHP using a binary installable package such as Marc Liyanage's PHP packages.
+ If you have installed another PHP package, you may have two versions of PHP and
+ PEAR installed on your system. To be sure which version you are using, type
+ <command>which pear</command> in your console to find out where PEAR is
+ located, and <command>pear -V</command> to find out some info about the pear
+ version, and also <command>pear config-show</command> to see the configuration
+ details.
+ </para>
+ <para>
+ If you have not made any modifications to the default Max OS X install, the PEAR
+ version you are running is the <filename>/usr/bin/pear</filename> which is
+ configured for the PHP 4 version distributed with OS X. If this is the case,
+ there are a couple options.
+ </para>
+ <para>
+ If you're using Marc Liyanage's PHP package, you might want to specify
+ <command>/usr/local/php5/bin/pear install {packagename}</command> (will probably
+ require sudo to install/upgrade packages), and always specify the full path when
+ you run pear & php through the console.
+ </para>
+ <para>
+ Or you could change every path for the OS X provided PEAR using config-set,
+ or, what I do is <command>sudo rm /usr/bin/php /usr/bin/pear</command> and then
+ <command>sudo ln -s /usr/local/php5/bin/php /usr/bin/php</command>
+ <command>sudo ln -s /usr/local/php5/bin/pear /usr/bin/pear</command> - which
+ will remove the PHP 4 version and link it to Marc Liyanage's PHP 5 version.
+ Keep in mind, Apple occasionally updates PHP on OSX, which will revert your
+ <filename>/usr/bin/php</filename> to their distributed version.
+ </para>
+ <simpara>
+ Note: It is uncertain if Apple will continue to distribute PHP version 4 for
+ Mac OS X <= 10.4. So these instructions may change, and may differ for your
+ specific version of Mac OS X. Always consult the Apple documentation to
+ understand the default install provided before making modifications.
+ </simpara>
+ </sect2>
+
+ <sect2 id="faq.windows">
+ <title>
+ Does PEAR work on windows?
+ </title>
+ <titleabbrev>
+ PEAR & Windows
+ </titleabbrev>
+ <para>
+ To make PEAR work on Windows, you simple need to add the PEAR
+ installation dir (e.g. <filename>c:\php\pear</filename>) to the
+ include_path directive in your <filename>php.ini</filename>.
+ </para>
+ <simpara>
+ Note: There are some classes (like Schedule/At.php), that do not
+ work on Windows, because they use *nix specific commands.
+ </simpara>
+ </sect2>
+
+
+ <sect2 id="faq.windows-build-out-of-date">
+ <title>
+ go-pear.php or bundled packages in the windows build of PHP 4.3.x is out of date!
+ </title>
+ <titleabbrev>
+ PHP 4.3.x pear bundle out of date
+ </titleabbrev>
+ <para>
+ Unlike other aspects of PEAR development, the windows build of PHP 4.3.x is not tracked
+ in CVS. Instead, it is located on the machine that builds windows snapshots. Often,
+ this will not be updated when the rest of PEAR is updated. Note that PHP 5.x releases
+ use a different build system and are automatically updated to the latest versions of
+ PEAR.
+ </para>
+ <para>
+ If you find that PHP 4.3.x has out-of-date versions of packages, or no longer works, then
+ please report that the windows bundle of PEAR is out of date to &email.pear.dev;
+ </para>
+ </sect2>
+
+
+ <sect2 id="faq.ssl-certificate">
+ <title>
+ Why does my browser show strange warnings when logging in to the website?
+ </title>
+ <titleabbrev>
+ SSL Certificate
+ </titleabbrev>
+ <para>
+ You are seeing the warnings because <literal>pear.php.net</literal>
+ uses a SSL key that is signed by <ulink url="&url.cacert;">CAcert</ulink>,
+ whose root certificate is unfortunately not bundled with most
+ browsers.
+ </para>
+ <para>
+ If you are using a Mozilla browser, you can import the certificate
+ <ulink url="&url.cacert.mozilla;">on this site</ulink> by clicking
+ on the link <quote>Root Certificate (PEM Format)</quote>. When
+ asked if you want to trust the new Certificate Authority, you need
+ to check at least the <quote>Trust this CA to identify web sites.</quote>
+ box and click "Ok".
+ </para>
+ <para>
+ People using Internet Explorer may find help <ulink url="&url.cacert.ie;">here</ulink>.
+ </para>
+ <para>
+ Mac OS X users must download the above mentioned PEM file. The
+ certificate can then be imported with the <quote>Keychain Access</quote>
+ utility via <quote>Import</quote> in the <quote>File</quote> menu.
+ </para>
+ </sect2>
+
+
+ <sect2 id="faq.read-only-folders-windows">
+ <title>
+ Installing into customized windows folders fails
+ </title>
+ <titleabbrev>
+ read-only isn't really read-only for customized windows folders
+ </titleabbrev>
+ <para>
+ To know that the folder has a customized view, Windows sets the
+ "read-only" attribute to the folder. The
+ "read-only" attribute is not actually used to control write
+ access. You can create files in a "read-only" folder.
+ <ulink url="http://support.microsoft.com/default.aspx?scid=kb;en-us;326549">
+ http://support.microsoft.com/default.aspx?scid=kb;en-us;326549</ulink>
+ </para>
+ <para>
+ The PEAR Installer detects the read-only attribute and refuses to install
+ into these folders. Unfortunately, there is no way to distinguish between
+ customized folders and actual read-only folders on Windows.
+ </para>
+ <para>
+ The work-around is to avoid installing PEAR packages into customized
+ Windows folders.
+ </para>
+ </sect2>
+
+
+ <sect2 id="faq.pearinhomedir">
+ <title>
+ I've got an old installation of PEAR and don't have the permissions to install a new version - what now?
+ </title>
+ <titleabbrev>
+ Installing PEAR in your home directory
+ </titleabbrev>
+ <para>
+ If <command>$ which pear</command> gives you something like <filename>/usr/local/bin/pear</filename>
+ and <command>$ pear -V</command> shows a very old version or if you don't want
+ to use it for other reasons, you have to install PEAR in your home directory.
+ </para>
+ <para>
+ Go to &url.pear.go;, save as <filename>gopear.php</filename> and do
+ <command>$ php gopear.php</command> or try
+ <command>$ lynx -source &url.pear.go; | php -q</command>.
+ </para>
+ <para>
+ Use <filename>/home/user/pear</filename> as prefix while installing PEAR, where user is your
+ username.
+ </para>
+ <para>
+ Once the installation is done, edit your PATH variable to include your planned new PEAR directory
+ <emphasis>before</emphasis> the old one.
+ </para>
+ <para>
+ For example put a <command>export PATH=/home/user/pear/bin:$PATH</command>
+ at the end of your <filename>~/.bashrc</filename> or <filename>~/.profile</filename>
+ under Linux. <command>$ echo $PATH</command> should give you now
+ <filename>/home/user/pear/bin:[...]</filename>
+ </para>
+ <para>
+ <command>$ which pear</command> should result in <filename>/home/user/pear/bin/pear</filename>
+ and <command>$ pear -V</command> something like "PEAR Version: 1.4.8"
+ (at the time of writing) or newer. Check the latest stable version at
+ &url.pear.package;PEAR under <emphasis>Current Release</emphasis>.
+ </para>
+ <para>
+ Now all you need is to set your <emphasis>include_path</emphasis> correctly, most
+ likely via
+ <programlisting role="php">
+ <![CDATA[
+ <?php
+ $path = ini_get('include_path');
+ ini_set('include_path', '/home/user/pear'.PATH_SEPARATOR.$path);
+ ?>
+ ]]>
+ </programlisting>
+ </para>
+ </sect2>
+
+ <sect2 id="faq.includepathproblems">
+ <title>
+ I have updated package X to get rid of errors like "undefined function Y",
+ but PHP still shows the error message(s). What's wrong?
+ </title>
+ <titleabbrev>
+ Errors still occur after package update
+ </titleabbrev>
+ <para>
+ It is very likely that you have defined two PEAR directories in your
+ <emphasis>include_path</emphasis>, and that you have updated the package
+ in the directory that is defined behind the first directory in your
+ <emphasis>include_path</emphasis>. If you either remove the wrong directory
+ from your <emphasis>include_path</emphasis> or change the order of the
+ directories in your <emphasis>include_path</emphasis>, the error messages
+ should not be shown anymore.
+ </para>
+ </sect2>
+
+ <sect2 id="faq.gopearnotparsed">
+ <title>
+ The downloaded go-pear.php isn't parsed by PHP! Why?
+ </title>
+ <titleabbrev>
+ Downloaded go-pear.php isn't parsed
+ </titleabbrev>
+ <para>
+ If you have followed <link linkend="installation.getting">the instructions
+ for getting go-pear.php</link> and you are using e.g. Windows and the
+ Internet Explorer, you might get the strange effect that -- although you
+ have named the file go-pear.php -- the file isn't parsed and the PHP source
+ code of it is shown.
+ </para>
+ <para>
+ The problem is that e.g. the Internet Explorer saves the file as a HTML
+ file with some HTML code around the PHP source code to display the code
+ nicely.
+ </para>
+ <para>
+ To avoid this problem, you should use the source code view of your browser,
+ e.g. by clicking with the right mouse key and selecting "Show source code"
+ from the context menu. If you save now the file that is shown in your
+ editor as go-pear.php, PHP will be able to parse the file properly.
+ </para>
+ <para>
+ Please note that the Windows versions of PHP have a file named <link
+ linkend="installation.getting">go-pear.bat</link> bundled. It is recommended
+ to use this batch file on Windows instead of using go-pear.php.
+ </para>
+ </sect2>
+
</sect1>
\ No newline at end of file