Re: how to deal with php5 only packages

You're now arguing that a package shouldn't be PHP5 because the reasons for using PHP5 aren't all that great. The last RC for PHP5 is out and it's inevitable that PHP5 will come into widespread use. No one on the "I'm against PHP5 ... because ... well I am!" crowd has answered this question: What is wrong with allowing a PHP5 package into PEAR and leaving it unstable until PHP5 is finally released? --Joe -- Joseph C. Stump joe@joestump.net http://www.joestump.net On Jun 16, 2004, at 1:42 PM, Lukas Smith wrote:

David Costa wrote:

Didn't we agree that the proposal of PHP 5 packages was fine as long as E_STRICT compliant and not stable till PHP 5 is ? You are free to recommend otherwise but I don't think that the approach "PHP 4 works, so why switch" is very progressive.

With PHP5 only you are shutting out most of the PHP world. This fact will change but I am sure you can come up with better reasons to use PHP5 than marking things private? Also your examples have yet to include examples where you would actually have to do more planning. regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07