The 2.4 branch of Apache has been available since February 12, but not available at Macports, which still defaults to versions 2.2. \u00a0Apache can be installed using the apache24 port, but connecting it to php55 calls in Apache 2.2, which isn’t what you’re after.<\/p>\n
This can be fixed with a port patch, as the problem is merely one of dependencies, not actual compatibility. \u00a0This patch\u00a0<\/a>\u00a0from the Macports bug list adds a new port php55-apache24handler, which is the code between PHP55 and the Apache 2.4 daemon, as the name suggests.<\/p>\n What isn’t necessarily clear I’ve explained here:<\/p>\n 1.\u00a0Where are portfiles?<\/strong><\/p>\n They’re in \/opt\/local\/var\/macports\/sources\/rsync.macports.org\/release\/tarballs\/ports<\/strong><\/p>\n where “\/opt\/local” is the default installation directory for Macports, which will be different only if you’ve installed it to a different place.<\/p>\n 2. \u00a0What are these portfiles?<\/strong><\/p>\n Within the …\/release\/tarballs\/ports directory are about 45 subfolders indicating the categories of ports. \u00a0Inside those folders are subfolders to find specific ports, although the categorization is not always what you would think. \u00a0For example, there’s a ‘lang\/php’ as well as a ‘php’.<\/p>\n A portfile is always named\u00a0Portfile<\/strong>.<\/p>\n 3. \u00a0What is a subport?<\/strong><\/p>\n This isn’t actually documented in the user documentation, but a “subport” is a port provided by a portfile with an extension name after a hyphen. \u00a0php55-apache2handler provides the\u00a0subport<\/em>\u00a0apache2handler.<\/p>\n 4. \u00a0Why I can’t find I find the php55 Portfile?<\/strong><\/p>\n A single Portfile can and often does provide multiple ports, as well as one or more subports. \u00a0In this case, ‘php\/Portfile’ provides a whole mess of ports, including the whole php series and many of its subports. \u00a0You can see this in the Portfile with references to “subports” in the Portfile, as well as the “PortGroup” instructions near the top, which include other port files.<\/p>\n 5. \u00a0Why doesn’t altering the Portfile Seem to do Anything?<\/strong><\/p>\n The entire system is cached with an index system. \u00a0cd to the “top level” of the ports tree at:<\/p>\n \/opt\/local\/var\/macports\/sources\/rsync.macports.org\/release\/tarballs\/ports<\/p>\n > portindex<\/strong><\/p>\n will regenerate the PortIndex and PortIndex.quick files you see there, and allow your port system to see any changes you’ve made.<\/p>\n 6. What happened to mod_wsgi?<\/strong><\/p>\n The mod_wsgi for interfacing to Python, should you want to do that, is still tied to Apache 2.2 in MacPorts.<\/p>\n <\/p>\n The release schedule for 2.4 (thanks, Apachehaus.com!) is:<\/p>\n 2.4.10 : July 19, 2014 Apache’s guide to doing the upgrade is here:<\/p>\n
\n2.4.9 : March 16, 2014
\n2.4.8 : Not Released
\n2.4.7 : Released November 25, 2013
\n2.4.6 : Released July 22, 2013
\n2.4.5 : Not released
\n2.4.4 : Released Feb 25, 2013
\n2.4.3 : Released Aug 18, 2012
\n2.4.2 : Released April 17, 2012
\n2.4.1 : Released February 17, 2012<\/p>\n