Re: svn: /pear/packages/Log/trunk/ package.php package.xml

2009/12/28 Helgi Þormar Þorbjörnsson <helgith@gmail.com>: > You can not presently drop PHP 4 support in a minor release like that unless I'm missing > some changed rules? > Please correct me if I'm wrong. That's unfortunate because the PEAR infrastructure appears to support such things. The problem that I am attempting to solve is thus: PHP5 introduced a deprecation warning for the '$a = &new' syntax that worked in (and is required by?) PHP4. Because this warning is emitted at compile-time, the syntax can't be conditionally based on a version_compare() result (which is how I work around the other PHP4 vs. PHP5 incompatibilities). This warning is only emitted under E_STRICT, but I don't think it's reasonable to continue asking all PHP5 users of the PEAR Log package to disable E_STRICT reporting. I think my options (as the Log package's maintainer) are therefore: - Continue doing nothing and expect PHP5 users to deal with the warnings. - Release 1.12.x as a PHP5-only package, dropping PHP4 compatibility. - Change '$a = &new' to '$a = new' and break PHP4 compatibility. - Create a new Log2 package that is PHP5-only. I assume the thing I'm supposed to do is release a Log2 package, but I'm reluctant to do that because: - Existing Log package users won't be automatically notified of the new package. - The Log2 package wouldn't offer anything new or otherwise compelling. - A "true" PHP5 Log2 package will require a lot of design work (which could wait for Log3). Another option would be for me to stop maintaining the Log package entirely and make this someone else's problem (such as the PEAR QA group), but would be neither productive nor server anyone's interests other than my own. -- Jon Parise (jon of php.net) :: The PHP Project (http://www.php.net/)