<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Bill,<div><br></div><div>Eventually…</div><div><br></div><div>There are some fundamental changes on how apache24 is installed as opposed to apache22.</div><div><br></div><div>Before I switched to MacPorts, I was running the 2.4.x branch on my personal machine. </div><div><br></div><div>So I installed apache24-devel, and found out of didn’t run out of the box. This issue was patched (<a href="https://trac.macports.org/ticket/44111">https://trac.macports.org/ticket/44111</a>), so apache24-devel now works.</div><div><br></div><div><div><div>On Jul 7, 2014, at 12:52 PM, Bill Christensen <<a href="mailto:billc_lists@greenbuilder.com">billc_lists@greenbuilder.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Just curious... I see that Apache 2.4.9 was announced in March (and that folks here have been working on a port of 2.4.x for 2 years: <a href="https://trac.macports.org/ticket/35824">https://trac.macports.org/ticket/35824</a>).<br><br>Any idea when the Apache2 port will get bumped from 2.2.27 to 2.4.x? The PCI compliance folks are complaining about my Apache version.<br><br>Thanks<br>_______________________________________________<br>macports-users mailing list<br><a href="mailto:macports-users@lists.macosforge.org">macports-users@lists.macosforge.org</a><br>https://lists.macosforge.org/mailman/listinfo/macports-users<br></blockquote></div><br><div>
<div>--</div><div>Marius Schamschula</div><div><br></div><br class="Apple-interchange-newline">
</div>
<br></div></body></html>