Re: about stability (upgrading pear...)

The dependency on xmlrpc is an optional dependency. PEAR 1.2.1 was incorrectly released as a stable release (it wasn't - there were several known bugs), and one of those bugs was the inability to differentiate between optional and required dependencies. Version 1.3 final will contain either a required dependency on PEAR 1.3b1 (the first version to fix this bug), or on XML_RPC package, when it finally integrates the ability to use xmlrpc-epi if it is available (Marshall, progress happening there?) Greg Stefan Neufeind wrote:

On 1 Dec 2003 at 12:55, Alberto M wrote:

when i tried to upgrade Pear I get this: admin:/usr/local/share/pear # pear upgrade PEAR downloading PEAR-1.3b3.tgz ... ...done: 86,146 bytes 'xmlrpc' PHP extension is not installed PEAR: dependencies failed the strange thing is that xmlrpc support is tagged as experimental. Thus, first question: how is possible to need an experimental PHP library ("Use at your own risk...") when installing main Pear package? At least, it's a strange thing.

[...] Hi, afaik this is just a problem of a dependency inside the package. If you have the pear-package XML_RPC installed this will also work without problems without the need for xmlrpc as a php-module. Although xmlrpc as a module is considered faster, the pear-package is fine as well. Unfortunately the dependencies are on xmlrpc (the module) currently. Simply install with pear upgrade --nodeps PEAR and you should be done. Regards, Stefan