[PATCH] configtest.php and PEAR packages

[alex@…]

A lot of reports point out that configtest.php didnt detect PEAR installed packages.

This is caused by the way how most linux distros manage PEAR modules installation. Packages didnt update central pear informations about installed modules (dependencies and versions are managed by the package system, not by PEAR).

This cause major trouble to the configtest.php script that relies on PEAR_Config and PEAR_Registry objects.

You can find here my proposed patch that let the script find modules, but at this time, cannot extract version.

[anonymous]

the patch

[rjl]

Note that this is effectively a duplicate of #306 (same issue). If indeed the problem is that some distros are not properly stocking the PEAR registry, though, why does running pear5 list work? Are these sites using a different registry that we need to query in a different way?

I suppose a crude solution might be to have the configtest.php script execute pear5 list and capture the output and parse it, the same way it parses the phpinfo() output. That would provide the version numbers and a list of the installed packages.

[alex@…]

My pear5 list is emtpy. So not sure what you're talking about

[alex@…]

On Gentoo, dev said :

Newer dev-php/PEAR-PEAR packages don't anymore install anything to .registry when installing a PEAR package via emerge, doing that gave various problem when people tried to upgrade/install/remove packages installed via emerge using the pear binary (as emerge doesn't know what packages are installed etc. manually using the pear command, and viceversa pear does not know what packages are installed through emerge).

Source

[rjl]

This particular problem may be unique to Gentoo, then. On Mandriva 2006 and SuSE 10.1, the pear5 list command shows all of the installed PEAR modules, but some of them (specifically PEAR::DB) don't seem to be detected properly via the PEAR registry object that configtest.php consults (see #306).

[anonymous]

Oh, delayed to 1.1.0 trunk.

Could you add a specific info at the top of the page warning the user about the possible no detection, depending how the linux distrib handle pear packages.