Re: pear installer in PHP 5.1 RC1

From: Date: Thu, 11 Aug 2005 10:53:10 +0000
Subject: Re: pear installer in PHP 5.1 RC1
References: 1  Groups: php.pear.core 
Request: Send a blank email to pear-core+get-3471@lists.php.net to get a copy of this message
On Thu, 11 Aug 2005 03:06:49 -0700 rasmus@lerdorf.com (Rasmus Lerdorf) wrote: > We can't put an RC1 out there until we fix the pear/XML_RPC issue. > Personally I'd like to completely get rid of it, but I see the > following options: > > 1. Put pear 1.4 into RC1 which means we can drop XML_RPC and go > REST 2. Force ext/xmlrpc to be mandatory and drop XML_RPC not possible. Certainly (if possible) in a 5.1.x, but we definitivally need more tests. There is still some issues (both about designs/features and bugs) that have to be solved before moving to a beta status. > 2. Force ext/xmlrpc to be mandatory and drop XML_RPC It could be nice to have it always installed. But it does not really make sense now as: . We will not use xmlrpc anymore in 1.4 and up . We tend to minimize the amount of extensions that cannot be disabled in php (or?) > 3. Fix XML_RPC to not suck Possible, but people should still rely on the ext. The lack of test cases does not help to provide a reliable alternative. As you pointed me out this morning, I will at least commit the tests. > 4. RC1 goes out with a pear installer than only works if people > compile with xmlrpc This is my favourite solution. I already asked to drop this dependency. Any serious xmlrpc usages should depend on ext/xmlrpc. > 5. Drop the pear installer completely from PHP 5.1 A big opposition unless we have a valid alternative. > It's been many weeks now and is at this point holding up RC1. Hmm? not really. Droping the xmlrpc package can be an annoyance for one or another, but it is definitivally not a stopping point to release RC1. > I'd actually like to see option 1. I know it isn't quite ready > yet, but perhaps we can get a few more people working on it and > make it ready. I can commit a day or two to it and I can bring > in a couple of developers from India as well if needed. But we'd > need to understand where the troublespots are and how much work > may be left. > > Option 2 would cause a number of people to freak out. Well > perhaps only Jani, but still. > > Option 3 may very well be the easiest, but we have been waiting > weeks for a fix on this one with multiple people saying they had > something, and we still don't see a fix. > > Option 4 is easy as well since Andi or I can do it on our own. > > I'd like to avoid option 5. I hate this option. This is again an attempt to drop something that many people starts to like or use. The installer is one thing, pear.php.net another. shot version, +1 for 4) here. Regards, --Pierre

« previous php.pear.core (#3471) next »