Date: Wed, 27 May 2015 22:47:22 +0200 From: olli hauer <ohauer@gmx.de> To: freebsd-ports@freebsd.org Subject: Re: Apache 2.4 must become default NOW Message-ID: <55662D5A.3030403@gmx.de> In-Reply-To: <5565D224.9060203@astart.com> References: <0E822D68-96E1-4328-9D00-1ADBF5671699@lists.zabbadoz.net> <53B9CD64.3010707@gmx.de> <20140706231559.GB8523@ivaldir.etoilebsd.net> <53C32862.601@sorbs.net> <5565D224.9060203@astart.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2015-05-27 16:18, Patrick Powell wrote:
> On 07/13/14 17:46, Michelle Sullivan wrote:
>> Baptiste Daroussin wrote:
>>> On Mon, Jul 07, 2014 at 12:27:48AM +0200, olli hauer wrote:
>>>
>>>> On 2014-07-05 19:09, Bjoern A. Zeeb wrote:
>>>>
<...snip..>
>> One would have hoped that mod_perl2 would have had this removed first:
>>
>> .if ${APACHE_VERSION} > 22
>> BROKEN= Does not build with apache24
>> .endif
>>
>> Just my small (557 packages) build set:
>>
>> ====>> Skipped ports: devel/bugzilla44 devel/p5-Log-Dispatch
>> www/p5-Apache-DBI www/p5-HTML-Mason www/p5-HTML-Mason-PSGIHandler
>> www/p5-MasonX-Profiler www/p5-RT-Authen-ExternalAuth www/p5-libapreq2
>> www/rt40
>>
>>
>> Michelle
>>
> I believe that this has been fixed for at least since Sept 2014. There is a 'test and debugging' version of mod_perl2 that appears to have the required mods/changes, but they have not been rolled into the upstream distribution.
>
> I wonder what happened to the mod_perl updating process...
>
At the moment the mod_perl2 port does the following.
- If apache22 is detected use the original 2.0.8 source to build mod_perl.
- if apache24 is detected a patch (50.000+ lines) will be applied to match upstream trunk r1638352.
Between r1638352 and the current rc1 changes for modperl_interp resulting in a non working apache24 with MPM event, a report for this can be read on the mod_perl-dev list.
--
olli
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55662D5A.3030403>