Skip to content
Find file
Fetching contributors…
Cannot retrieve contributors at this time
70 lines (68 sloc) 2.01 KB
<?xml version="1.0" encoding="UTF-8"?>
<package version="2.0" xmlns="http://pear.php.net/dtd/package-2.0" xmlns:tasks="http://pear.php.net/dtd/tasks-1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://pear.php.net/dtd/tasks-1.0
http://pear.php.net/dtd/tasks-1.0.xsd
http://pear.php.net/dtd/package-2.0
http://pear.php.net/dtd/package-2.0.xsd">
<name>PEAR_Exception</name>
<channel>pear.php.net</channel>
<summary>The PEAR Exception base class</summary>
<description>
PEAR_Exception PHP5 error handling mechanism
Consider using PEAR2_Exception from http://pear2.php.net if you are developing for PHP 5.3+
</description>
<lead>
<name>Helgi Thormar</name>
<user>dufuz</user>
<email>dufuz@php.net</email>
<active>yes</active>
</lead>
<developer>
<name>Greg Beaver</name>
<user>cellog</user>
<email>cellog@php.net</email>
<active>no</active>
</developer>
<date>2011-03-24</date>
<version>
<release>1.0.0beta1</release>
<api>1.0.0</api>
</version>
<stability>
<release>stable</release>
<api>stable</api>
</stability>
<license uri="http://opensource.org/licenses/bsd-license.php">New BSD License</license>
<notes>
This packge was split out from the PEAR package. If you use PEAR_Exception in your package
and use nothing from the PEAR package then it's better to depend on just PEAR_Exception.
</notes>
<contents>
<dir name="/">
<dir name="PEAR">
<file name="Exception.php" role="php">
<tasks:replace from="@package_version@" to="version" type="package-info" />
</file>
</dir>
<file name="LICENSE" role="doc" />
</dir> <!-- / -->
</contents>
<dependencies>
<required>
<php>
<min>4.4.0</min>
<exclude>5.0</exclude>
<exclude>5.1.0</exclude>
<exclude>5.1.1</exclude>
<exclude>5.1.2</exclude>
<exclude>5.1.3</exclude>
<exclude>5.1.4</exclude>
<exclude>5.1.5</exclude>
</php>
<pearinstaller>
<min>1.9.3</min>
<exclude>1.9.3</exclude>
</pearinstaller>
</required>
</dependencies>
<phprelease/>
</package>
Something went wrong with that request. Please try again.