[php-maint] Bug#443524: Bug#443524: Bug#443524: php-pear: manually installed PEAR modules shouldn't go to /usr/share/php

[Thomas Goirand]

On 03/18/2011 09:13 PM, Olivier Berger wrote:
> On Sun, Jan 27, 2008 at 03:09:07PM +0100, Gregory Colpart wrote:
>> Hello,
>>
>> On Fri, Jan 25, 2008 at 03:43:20PM +0100, Christian Hammers wrote:
>>>
>>> After stumbling over the same bug I would proposed to simply set the
>>> defaults in /etc/pear/pear.conf to /usr/local/ dirs. I did this for
>>> my server with "pear config-set" and it seems to work.
>>>
>>> Mixing Debian packages and pear installed libraries quickly turns
>>> into a mess if the directories are not clearly separated!
>>
>> I fully agree with this proposal however the main problem is that
>> pear can't deal with two directories and it breaks some webapps
>> setup (for example, function get_installed_pear_packages() in
>> eGroupWare could be broken).
>>
> 
> Then shouldn't the packaging for these apps be fixed so that they
> depend from the right place where these PEAR libs would belong
> depending if they are packaged already or not ?
> 
> I think you may not expect that manually installed web apps can run
> on a Debian system unchanged if they depend on a mix of packaged
> and non-packaged PEAR dependencies.

IMHO, the way to fix it, is to do these missing Debian packages. Hacking
a PEAR Debian package is quite easy, if you only care that it works and
if you don't look into having uploaded to Debian!

Hacking with 2 PEAR directory will only lead with loads of issues, like
one PEAR library depending on another and not being able to find it
where it is expected...

Thomas