Re: [PEAR] [ANNOUNCEMENT] PEAR_Exception-1.0.0beta1 (beta) Released.

[email protected] (Alexey Borzov)
Newsgroups php.pear.dev,php.pear.general
Message-ID <[email protected]>
Hi,

Helgi (or whoever released this), is this a good idea to do a separate 
PEAR_Exception without releasing a new PEAR package simultaneously? Current PEAR 
package contains PEAR_Exception class as well and this will probably lead to 
conflicts.

I don't quite remember what was the consensus last time this was discussed, but 
from my point of view the best solution will be to push a new PEAR 1.10.*
  * with dependency on PHP 5+
  * without bundled PEAR_Exception class but
  * with a required dependency on new PEAR_Exception package.

This way packages that currently have to depend on PEAR package can easily be 
updated to depend on PEAR_Exception and won't break in the transition process.

Also a new version of PEAR is long overdue with 1.9.4 released in 2011 and 82 
(!) bugs in the tracker.

Is anyone working on PEAR at all? If not I may help a bit with bug triage and 
possibly send some patches.


On 21.02.2014 22:37, PEAR Announce wrote:
> The new PEAR package PEAR_Exception-1.0.0beta1 (beta) has been released at http://pear.php.net/.
>
> Release 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.
>
> Package Info
> ------------
> PEAR_Exception PHP5 error handling mechanism
>
>   Consider using PEAR2_Exception from http://pear2.php.net if you are developing for PHP 5.3+
>
> Related Links
> -------------
> Package home: http://pear.php.net/package/PEAR_Exception
>     Changelog: http://pear.php.net/package/PEAR_Exception/download/1.0.0beta1
>      Download: http://download.pear.php.net/package/PEAR_Exception-1.0.0beta1.tgz
>
> Authors
> -------
> Helgi Гћormar ГћorbjГ¶rnsson <[email protected]> (lead)
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.