eaccelerator is not suppose to block zend, eaccelerator only need to be loading before zend, this is my file to loading eaccelerator, zend and ioncube loader:
There's no way to ensure what gets loaded first via what we have available in eclasses, plus - this is just totally pointless IMO. Use one or the other, or maintain it in your overlay, we are not going to support this at the moment.
point of loading this 3 extention is that IPB using eaccelerator, another script is encoded by zend another by ion
(In reply to comment #2)
> point of loading this 3 extention is that IPB using eaccelerator, another
> script is encoded by zend another by ion
Well, that must be a PITA to maintain. :P
Anyway as noted above, this would require a significant rewrite of php-ext-base-r1.eclass to make it possible to ensure sane ordering and more flexibility with these php.ini files, otherwise people will get broken PHP, non-starting apache and all similar kind of nasty stuff.
Maybe when PHP6 gets in. Thanks. :)
I solved the ordering issue by putting all my eaccelerator related settings in a file called /etc/php/apache2-php5/ext/eaccelerator.ini and all my Zend Optimizer related settings in /etc/php/apache2-php5/ext/zendoptimizer.ini (and ofcourse linking them in ext-active)
The alphabet takes care of the ordering :) , since the letter e comes before the z (and the ini files seem to get imported by php in alphabetical order). This may be a nice fix for the ebuild for now.
(In reply to comment #4)
We have some ideas including using ## prefixes for the config files (like, 30-eaccelerator.ini), nevertheless this requires making this functionality actually available in the appropriate eclasses and adjusting all ebuilds accordingly. Alphabetical ordering doesn't fly that much with different locales. :)