IMP breakage?

[Bruno Afonso]

Ok, it seems the include path did the trick. So I can happily report imp 
seems to be working fine with the actual port tree structure, with not 
external tweaking and simply compiling imp from ports. All I did was 
setup portupgrade for the ports imp and turba not to include ldap 
backend support and to use courier imap instead of default uw-imap.

I did not need any settings in make.conf :)

would be nice if someone could confirm imp (latest version) is working 
100% too.

BA

Nagilum wrote:
> Matthew Seaman wrote:
> 
>>> From my own experience I can only advice against setting 
>>> WANT_PHP_PEAR in /etc/make.conf!
>>> http://groups.google.de/groups?q=FreeBSD+php4-pear+broken&hl=de&lr=&ie=UTF-8&selm=cdt34h%241g4o%241%40FreeBSD.csie.NCTU.edu.tw&rnum=1 
>>>
>>> ..and other php related threads right now.
>>> In fact I removed all my old php specific stuff from /etc/make.conf.
>>>   
>>
>>
>> Ah -- good call.  Does it work to use WANT_PHP_PEAR on the make
>> command line instead?  I'm beginning to think the WANT_PHP_FOO
>> variables maybe should be divided up a bit further into more clearly
>> demarkated porter-only USE_PHP_FOO and user-only WITH_PHP_FOO or
>> WANT_PHP_FOO versions.
>>
>>  
>>
> You don't need to use WANT_PHP_PEAR at all I think. At least I didn't 
> need it.
> 
>>> at I did was pkg_delete pear\* and then reinstall php4, php4-pear, 
>>> php-extensions (do a "make config" there) pear-PEAR and all required 
>>> pear modules (try http://yourside/horde/test.php and 
>>> http://yourside/horde/imp/test.php !)
>>> Unfortunately this means imp will be offline for a few hours it takes 
>>> to build all this stuff.
>>> After that everything should be swell again, I'm still running 
>>> horde-2.2.5 + imp, because the php update was enough for one weekend 
>>> .-). Maybe I'll update horde/imp when both have been updated but so 
>>> far I see no need as everthing works fine (even pkgdb -F has nothing 
>>> to complain).
>>>   
>>
>>
>> Ho hum.  I'm not running Imp, but I hit the same sort of problems with
>> some code of my own.  Installing lang/php4-pear was required, and I
>> have a feeling I had to tweak some settings in php.ini to get the pear
>> stuff to work -- independent of the tweaks required to make the php
>> extensions load up properly.  But YMMV.
>>  
>>
> Yeah, but it is mentioned when devel/php4-pear installs:
> 
>   include_path = ".:/usr/local/share/pear"
> 
> When I installed the php-extensions I also had to adjust this:
> 
>  extension_dir = "/usr/local/lib/php/20020429/"
> 
> 

-- 
Bruno Miguel Afonso
Biological Eng. student
D.E.Q. @ I.S.T. - Portugal
http://dequim.ist.utl.pt/~bruno/