Hi,
I think I did not said things correctly.
If I try to emerge any PEAR package, to install it the system tries to
use /usr/bin/pear which does not get installed exactly because PHP is compiled
without PEAR. I mean the pear core which can be used to install other pear
packages.
Actually if you look in the php5-sapi-r3.eclass you will see something like
this:
rm -rf ${D}/usr/bin/{phpize,php-config,pear}
rm -rf ${D}/usr/lib/php/build
rm -rf ${D}/usr/include/php
It seems the installation of the latest php, which I use (it's devel system
and I want
to have the latest possible PHP to test and develop for the future:)) deletes
the pear stuff.
As I said previously, I could tweak the .eclass myself but I don't want to
do that since
I would have to do it on every upgrade.
That is why I would have preffered to have a clear option whether to
install PEAR upon
PHP installation or not in the form of a USE flag. This would be the nicest and
cleanest way.
Catalin
Craig Duncan wrote:
> Catalin Trifu wrote:
>
>
>> Hi,
>>
>> I have PHP unmasked in package.unmask, so when I install it I get PHP
>> 5.1.0b2
>>which is exactly what i want.
>> But there is not PEAR installed with it, which is not what I want. There
>>is no USE flag to install PEAR or not. I looked in
>>/usr/portage/eclass/php5-sapi.eclass and
>>in php5-sapi_src_compile I found:
>>
>> php5-sapi_is_providerbuild || my_conf="${my_conf} --without-pear"
>>
>> I have no idea where php5-sapi_is_prviderbuild comes from.
>> Is there a way to install pear without tweaking the .eclass file because it
>> gets overwritten
>>every time emerge sync ?
>> Perhaps a USE flag would be much more appropiate that the internal flag.
>>
>>
>>Catalin
>>
>>
>>
>
> All pear packages are in separate ebuilds, either lok in
> /usr/portage/dev-php or use
> $ esearch PEAR-
>
> to find all available pear packages on your system.
>
> Craig
--
[email protected] mailing list
