If you have finished experimenting with a PEAR package, have decided to use another solution, or have no more use for the package, you should uninstall it from the system. Doing so is trivial using the uninstall command. The general syntax follows:
%>pear uninstall [options] package name
For example, to uninstall theNumbers_Romanpackage, execute the following command:
%>pear uninstall Numbers_Roman
If other packages are dependent upon the one you’re trying to uninstall, a list of dependencies will be output and uninstallation will fail. While you could force uninstallation by supplying the-n(--nodeps) option, it’s not recommended because the dependent packages will fail to continue working correctly. Therefore, you should uninstall the dependent packages first. To speed the uninstallation process, you can place them all on the same line, like so:
%>pear uninstall package1 package2 packageN
Downgrading a Package
There is no readily available means for downgrading a package via the Package Manager. To do so, download the desired version via the PEAR Web site (http://pear.php.net/), which will be encapsulated in TGZ format, uninstall the presently installed package, and then install the downloaded package using the instructions provided in the earlier section “Installing a PEAR Package.”
Summary
PEAR can be a major catalyst for quickly creating PHP applications. Hopefully this chapter convinced you of the serious time savings this repository can present. You learned about the PEAR Package Manager and how to manage and use packages.
Later chapters introduce additional packages, as appropriate, showing you how they can really speed development and enhance your application’s capabilities.
DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.
