CiviCRM Community Forums (archive)

CiviCRM includes its own PEAR libraries in the /packages folder. If other modules attempt to use the system PEAR, we'll get a "cannnot redeclare class" error. At this point, I'm stuck as to an easy workaround for this.

I understand why Civi includes its own PEAR library for compatibility reasons, but I wonder how easy it would be to set the option for Civi to use the system PEAR libraries (and leave it up the the sysadmin to ensure compatibility). This will allow Civi to play nice alongside other modules that depend upon PEAR classes.