Hello Laurent,
I don't know about the currently planned versions for
PEAR_PackageUpdate, but remember that you must not break backward
compatibility with higher versions (except when going from stable to a
higher, unstabler version and planning to add the removed features in
until the next stable one).
Hello Christian,
There is no break backward compatibility in PEAR_PackageUpdate. In PEAR CVS I've commited few lines of code (for future version 1.1.0) that I've removed only to allow me to publish the stable and bug fix version 1.0.1
And for PHP_CompatInfo, there will be also no break BC due to the solution I've found !
Except if you consider that changing File structures is a break BC !
I should release the new beta 2 of version 1.8.0 tomorrow
Until then I'll commit an example to demonstrate that PCI usage is almost the same as previously versions.
Thanks again, to take time to reply to my post :)