Arnaud Limbourg wrote:
This package is just a nightmare.
I started the job, so naturally hooked on the package.xml where I
already fixed the example file name and put a right date so pear
install package.xml could work.
Actually the install path is now conform (XML/CSSML...) what breaks
BC as it was previously under XML_CSSML !
Dunno if the installer can build a link to correct this ...
The package.xml hasn't changed much in the past two years and the
install dir as
always been correct. The file gets installed as XML/CSSML.php which is
Wish me courage and luck :)
I wonder if we shouldn't go the "BIG WARNING with a dep on PHP4 and
with a dep on PHP5" way, using $this is so wrong. Would it break many
is the question.
Another question occurs which will perhaps solve the problem:
Can sound strange for many people, but I allways build my tests *before*
trying to repair such catasthrops.
So, I need a PHP5 with the domxml extension. It appears, domxml is no
more bundled in php but exists only as pecl extension. 
Now, and it was confirmed by chregu on IRC:
"This extension allows you to operate on an XML document with the DOM
API. It has been superseded by the DOM extension that ships with PHP 5.
Although it should be possible to use this old domxml extension with PHP
5, its use is highly discouraged, as there a very high potential for
conflicts with the new dom extension." 
So, half of the package is deprecated on PHP5 , the other half depending
What means, quite no other solution exists than:
1) releasing a PHP4 only fixbug, with no changes , or quite
2) creating a PHP5 (and perhaps PHP4 compat) new XML_CSSML2 if not
This new package could make use of the bundled DOM  instead of domxml
* it could perhaps be possible to use pear installer new features to
have a different installation depending on the php version
* the class could test for the existence of domxml or dom functions and
call the corresponding driver.
bertrand "toggg" Gugger