On 1 mai 09, at 00:26, Ryan Schmidt wrote:
On Apr 30, 2009, at 01:28, Ryan Schmidt wrote:
On Apr 27, 2009, at 09:29, alaka...@macports.org wrote:
Revision: 50191
http://trac.macports.org/changeset/50191
Author: alaka...@macports.org
Date: 2009-04-27 07:29:29 -0700 (Mon, 27 Apr 2009)
Log Message:
-----------
Migrate php5-eaccelerator to the php5extension PortGroup
Did you try whether the port still works? I haven't tried it yet
but I didn't think this would work because eAccelerator is not a
normal PHP extension but a Zend extension and therefore needs to be
loaded with the zend_extension directive and not the extension
directive. I was going to add an option to the php5extension
portgroup to allow you to specify what type of extension it is so
that the correct directive can be written to the .ini file.
I had tried it and it worked (if I'm not mistaken), but had forgotten
about this distinction.
Ok, it looks like eAccelerator is unique in that it can be used as
either a Zend extension or as a regular extension, which is why it
still works with the portgroup:
Lucky me :p
http://eaccelerator.net/wiki/InstallFromSource#Step3.ConfiguringeAccelerator
But I can't tell which method is preferred or why.
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...
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
