Re: Forking PEAR

On Jul 15, 2004, at 9:58 AM, Stephan Wentz wrote:

Hmm I think you misunderstood me - all the packages I *need* aren't E_STRICT! Not _every_ PEAR-package! Ok, this was a little unclear stated by me ;-)

I think you are a but confused. Any PHP 4 package cannot run under E_STRICT in PHP 5. So Almost all PEAR packages today ( which are PHP 4 compatible ) won't run on E_STRICT PHP 5. It Don't expect that this fork idea will make developer porting to PHP5. You will be in the same situation because if I have a PHP 4 package and don't want/have the time etc. to release a PHP 5 version you can't force me.

Not you. But maybe someone else would! Then he can do it even now.

So the whole argument in my opinion is just flawed and based upon false assumptions. Everyone is talking about what is he doing and how hard is to cope, well I have been working on PHP 5 packages and we both know that the majority of hosts /settings won't run under E_STRICT anyway and so you can run your application safely. You can't expect all the packages to be ported to PHP 5 after two days.

Not really. But I would contribute and do my best to get the packages I need to PHP5. That's what it's about, eh? Contributing... In the moment the only people satisfied are these sticking to PHP4. But what do you think new developers will think when they want to develop a PHP5-app? PEAR won't be of any use to them. Because the majority is PHP4-only. I don't think anyone wants to stick with PHP 4 for the sake of it. There are some developers who prefer to work on PHP 5 when it will be widely adopted and seems very reasonable to me ;)

Don't get me wrong, I see your point but the forking will be a total waste of time, resources etc. Cheers David Costa