Re: installing HTTP_Request

From: Date: Thu, 06 Dec 2007 00:26:41 +0000
Subject: Re: installing HTTP_Request
References: 1 2 3  Groups: php.pear.general 
Request: Send a blank email to pear-general+get-28283@lists.php.net to get a copy of this message
Bennett Haselton wrote: > At 07:49 PM 12/5/2007 +0100, Christian Weiske wrote: >> > >How likely is it that four randomly selected machines would all have >> > >a broken PEAR installation on them? Is there perhaps a deeper >> > >problem here? >> >> PEAR 1.3.2 is pretty old and the new channel.xml probably causes >> problems with this antique version. > > Heh, is that normal -- that if a version is deployed on (apparently) the > majority of machines on the Internet, that the project not only drops > support for that version, but drops support for *upgrading* from that > version? > > I hope they might consider making the upgrade backward-compatible with > 1.3.2 at some point. > > Well I offered RentACoder.com $25 for anyone who could write me a PHP > function that returns 1 or 0 for a working/nonworking URL without using > PEAR packages; in the meantime, starting with the instructions at > http://pear.php.net/manual/en/installation.php > should I uninstall PEAR before attempting to re-install it? i.e., what > exactly should I do to uninstall PEAR, and then which of the pages > linked from http://pear.php.net/manual/en/installation.php > should I > start following the steps on to install the latest one? PEAR 1.3.2 was buggy in some serious ways. The earliest fully functioning version of PEAR is 1.3.3. The bugs you are experiencing are some of the reasons we have released newer versions. You are also using a very old version of PHP, one that has many known security vulnerabilities, that may be of greater concern than the upgrading of PEAR, were I in your shoes. As for making it possible to upgrade from 1.3.2, it is possible, but the problem is that 1.3.2 has so many serious bugs in it, it is not capable of doing an upgrade properly, and will leave your system corrupted. This is not something that can be fixed, except by upgrading. Incidentally, the majority of machines - active machines - on the internet are using PEAR version 1.5.0 or newer, in fact upwards of 99.8%, based on the apache server logs at pear.php.net, so the fact that you are using 1.3.2 puts you in a rather severe minority :). Greg

« previous php.pear.general (#28283) next »