[50191] trunk/dports/php/php5-eaccelerator/Portfile

[Olivier Le Floch]

>> I think using it as a regular PHP extension is better for stability  
>> reasons :
>>
>>> http://bugs.php.net/bug.php?id=42002#c128772
>>
>> But I really can't find anything more regarding this issue...
>
> That ticket doesn't seem to have reached a meaningful conclusion...  
> "No feedback"...

I was actually just (more specifically) referring to derick at php.net's  
comment :
> Do not file bugs when you have Zend extensions (zend_extension=)  
> loaded. Examples are Zend Optimizer, Zend Debugger, Turck MM Cache,  
> APC, Xdebug and ionCube loader. These extensions often modify engine  
> behavior which is not related to PHP itself.
> My research suggests that a zend extension would perform faster, but  
> that some zend extensions cannot be used with other zend extensions,  
> so it would be more compatible to load eAccelerator as a php  
> extension to avoid that issue.
>
> Maybe on ports that can be loaded either as a zend extension or as a  
> php extension, we should be providing variants to allow the user to  
> choose? with php extension being the default? Though I'm inclined to  
> do nothing, and just leave it as a php extension, until someone  
> complains.

That's also my take on this issue ; I'm not sure many people will  
encounter performance problems with eaccelerator that would be best  
adressed by switching it to a zend extension.