[pkg-php-pear] php-xml-beautifier

[Thomas Goirand]

On 04/02/2012 12:26 AM, Mathias Ertl wrote:
> Thomas,
> 
> On 2012-03-30 21:59, Thomas Goirand wrote:
>> On 03/20/2012 05:25 PM, Mathias Ertl wrote:
>>> ...
>>
>> Mati,
>>
>> FYI, I have finally fixed XML_Parser, and uploaded version 1.3.4-2 with
>> the correct patch so that there's no "PHP Strict Standards" issues
>> anymore. If you want to rework on XML_Beautifier since some work has
>> been done on it, please go ahead, but currently, it does:
>>
>> zigo at GPLHost:xen01/node0184>_
>> /usr/share/doc/php-xml-beautifier/XML_Beautifier/examples$ php example1.php
>> PHP Fatal error:  Call to undefined method
>> XML_Beautifier_Tokenizer::XML_Parser() in
>> /usr/share/php/XML/Beautifier/Tokenizer.php on line 112
>>
>> I'm not sure how to fix that... (but notice that the XML_Parser errors
>> are now gone!)
> 
> The main problem is that I found statements by the maintainers in their
> bugtracker that they consider this a PHP 4 library. Yes, PHP 4.

This looks like that it's the same (stupid) guy that was leading
XML_Parser. If you have a look at pear.php.net, they are now deprecating
XML_Parser, in the favor of XML_Parser2, which is fixing all the issues,
but which has the same core code. I believe that XML_Parser2 is really
much much better, and it seems to me that someone else (from the PEAR QA
team) took over and fixed what was needed.

> I am too
> lazy to look that up now, but I found several bugs that where closed
> just because they where regarding PHP 5 compatibility.

That's plain bullshit and laziness from the maintainer, and quite
unacceptable, IMO. PHP4 is long gone, and no security support is there.
It must be full of security holes.

> I think (correct me if I am wrong) that this makes the software in
> general unsuitable for Debian unstable?

That's correct, but you can still work on it yourself and fix the issues
so that it works with PHP5. I would understand though, if you didn't
have time for it.

Thomas