[ 
https://issues.apache.org/jira/browse/LOG4PHP-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227653#comment-13227653
 ] 

Bruce Ingalls commented on LOG4PHP-173:
---------------------------------------

I am not a PEAR expert, myself. I am likely ranting to the wrong people. Other 
packaging systems have hashes or signing, hopefully, php.net will catch up.
The best I know of for PEAR, is to break 5.2 compatibility, package as PHAR, 
which allows checking local file size against the server.
I am testing on an older 5.2.x, and the good news is that log4php does support 
it. PHP_CompatInfo is a CodeSniffer plugin, to test the minimum theoretical 
supported version (5.2.0). I will soon upgrade my requirements.
I've not the skills, nor communication with pear.php.net to fix that problem, 
but I am donating code that is every bit as interesting as the recent Apache 
Chainsaw (or LogFactor 5?) support.
                
> Minimum PHP version requirement
> -------------------------------
>
>                 Key: LOG4PHP-173
>                 URL: https://issues.apache.org/jira/browse/LOG4PHP-173
>             Project: Log4php
>          Issue Type: Dependency upgrade
>          Components: Documentation
>    Affects Versions: 2.2.1
>         Environment: PHP v5.2.26
>            Reporter: Bruce Ingalls
>              Labels: documentation
>             Fix For: 2.2.1
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Documentation claims that Log4php supports PHP v5.2. The simplest example in 
> quickstart works for v5.3, but fails for v5.2.26:
> Fatal error: Call to a member function close() on a non-object in 
> ~PEAR/log4php/Logger.php on line 302
> Further, your unit testing section at 
> http://wiki.apache.org/logging-log4php/WritingTests uses phpunit, which 
> requires PHP v5.2.27+
> This implies that you are not testing older versions of PHP, unless you've 
> built a legacy test harness.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to