Re: Apache 24 + mod_perl

Steve Hay <[email protected]>
Newsgroups gmane.os.freebsd.devel.ports,gmane.comp.apache.mod-perl
Message-ID <CADED=K7Y2rMobduFW+AdQrKOHjBBCO+zKi=p9N+ib03LCufJRw@mail.gmail.com>
On 3 August 2014 22:13, Patrick Powell <[email protected]> wrote:
> On 08/03/14 08:25, olli hauer wrote:
>>
>> On 2014-08-01 23:34, Kurt Jaeger wrote:
>>>
>>> Hi!
>>>
>>>> Question:  when will mod_perl be available for Apache 24?
>>>
>>> There's a PR where people are discussing this:
>>>
>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191471
>>>
>>> This PR needs more testers etc.
>>>
>> I've updated the PR with a patch against the latest mod_perl trunk
>> revision (r1602105).
>>
>> The patch against the port can be grabbed from here or from our bugzilla
>>
>> http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff
>>
>> Please test *at own risk*, and report issues to upstream and here so we
>> can integrate fresh upstream fixes and update the port.
>>
>> The first proposed patch will allows the port to build but I have to many
>> concerns for integrating this simple fix into the tree.
>> I don't believe the first patch on the PR will work right else it would
>> take the upstream dev. work and time for mod_perl2 at absurd-um ...
>>
>>
> I have taken a slightly different approach,   using the mod_perl2 SVN
> ..../httpd24 branch as the starting point.
>

The httpd24 branch is obselete. It was used for the initial
development of httpd-2.4 support, but was superseded by
httpd24threading, and since then everything from both branches has
been merged back to trunk.

The current trunk is largely ready for a 2.0.9 release supporting
httpd-2.4, pending some more testing and fixes as necessary.
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.