On 01/07/2016 01:40 PM, Sebastiaan Lokhorst wrote:
Are you sure your GroupWare app needs PEAR? PEAR is usually only used to
install dependencies, which can also be done in some other way.
Yes,
It is a required part of the setup/install routine. For the current
egroupware 14 branch, the required pear packages are needed:
Installed packages, channel pear.php.net:
=========================================
Package Version State
Archive_Tar 1.4.0 stable
Auth_SASL 1.0.6 stable
Console_Getopt 1.4.1 stable
DB 1.8.2 stable
HTTP_Request 1.4.4 stable
Log 1.12.9 stable
MDB2 2.4.1 stable
MDB2_Driver_mysql 1.4.1 stable
MDB2_Driver_mysqli 1.4.1 stable
Mail 1.2.0 stable
Math_BigInteger 1.0.2 stable
Net_DNS2 1.4.1 stable
Net_IMAP 1.1.3 stable
Net_SMTP 1.6.3 stable
Net_Socket 1.0.14 stable
Net_URL 1.0.15 stable
PEAR 1.9.5 stable
Structures_Graph 1.0.4 stable
Text_Figlet 1.0.2 stable
XML_Feed_Parser 1.0.5 stable
XML_SVG 1.1.0 stable
XML_Util 1.2.3 stable
For the previous 1.8 branch, the following are needed:
Installed packages, channel pear.php.net:
=========================================
Package Version State
Archive_Tar 1.3.11 stable
Auth_SASL 1.0.6 stable
Console_Getopt 1.3.1 stable
DB 1.7.14 stable
Log 1.12.7 stable
MDB2 2.4.1 stable
MDB2_Driver_mysql 1.4.1 stable
MDB2_Driver_sqlite 1.4.1 stable
PEAR 1.9.4 stable
Structures_Graph 1.0.4 stable
XML_Feed_Parser 1.0.5 stable
XML_Util 1.2.1 stable
It would take hacking the eGroupWare installer to bypass the pear
requirement. I was the one that got bit by the conflicting files installed by
the pear Console_Getopt package. (see 12/20/15 post).
# pear list-files Console_Getopt
Installed Files For Console_Getopt
==================================
Type Install Path
php /usr/share/pear/Console/Getopt.php
test /usr/share/pear/test/Console_Getopt/tests/001-getopt.phpt
test /usr/share/pear/test/Console_Getopt/tests/bug10557.phpt
test /usr/share/pear/test/Console_Getopt/tests/bug11068.phpt
test /usr/share/pear/test/Console_Getopt/tests/bug13140.phpt
However, now that the source of the conflict is known, I would a lot rather
have a php-pear package and manage any conflicts that arise, as opposed to not
having the package and having to use the generic pear install or build a
package. Either way, the package will still be needed.
--
David C. Rankin, J.D.,P.E.
