perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jie Gao <J....@sydney.edu.au>
Subject Re: Apache 24 + mod_perl
Date Thu, 07 Aug 2014 02:43:25 GMT
The patch, or rather the patching itself, does not work with a box of
Red Hat Enterprise Linux Server release 6.5 for me here.

Regards,

Jie 

* Patrick Powell <papowell@astart.com> wrote:

> Date: Wed, 6 Aug 2014 17:27:15 -0700
> From: Patrick Powell <papowell@astart.com>
> To: olli hauer <ohauer@gmx.de>
> CC: Steve Hay <steve.m.hay@googlemail.com>, Kurt Jaeger <lists@opsec.eu>,
>  ports@freebsd.org, "modperl@perl.apache.org" <modperl@perl.apache.org>
> Subject: Re: Apache 24 + mod_perl
> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130714
>  Thunderbird/17.0.7
> 
> On 08/06/14 14:34, olli hauer wrote:
> >On 2014-08-06 22:45, Patrick Powell wrote:
> >>On 08/06/14 00:19, Steve Hay wrote:
> >>>On 3 August 2014 22:13, Patrick Powell <papowell@astart.com> 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 absurdI -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.
> >>>
> >>I tried using the trunk a couple of days ago and it did not compile.  Just to
make sure
> >>that I am using the right SVN respository and branch, what is the URL of the
trunk SVN repository?
> >>I am more than happy to try testing mod_perl.
> >>
> >Hm, with the following patch applied to www/mod_perl2 it builds fine for me on FreeBSD
8.4 / 10.0 (amd64) an apache-2.4.10
> >http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff
> >
> >The patch does some adjustments in the port / pkg-plist and fetches a complete archive
containing all patches so the sources are the same as the upstream (r1602105) trunk/httpd24threade
branch.
> >
> >After applying the patch and using the command `make patch' it is easy to compare
the sources against upstream sources (check out before)
> >http://svn.apache.org/repos/asf/perl/modperl/branches/httpd24threading
> >http://svn.apache.org/repos/asf/perl/modperl/trunk
> >
> >
> >Easiest way to apply the patch against the unmodified port:
> >
> >$ cd www/mod_perl2
> >$ fetch http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff
> >$ patch -p1 < mod_perl2-2.0.8_apache24.diff
> >
> >PS:
> >I've updated the patch because it needs some additional handling for pkg-plist if
build against apache-2.2.x (Provider.pm/Provider.so)
> >
> >
> I tried your procedure (see above).  The patch applied, I was able
> to compile the mod_perl,
> and  'make test' ran and it passed all of the critical tests.
> 
> I then ran some more of my tests for the functionality it used.
> These passed.
> 
> I would say that unless somebody else comes up with a problem that I
> would use this as a baseline
> for distribution/installation.
> 
> That is,  I would put up the modified Makefile,  with a warning, but
> would allow people
> to make/install it by specifying an option such as "make IGNORE_WARNING=yes"
> 
> Of course, the FreeBSD Ports team may have different views on
> this... but until the upstream mod_perl team puts out mod_perl-2.0.9
> officially I think that this is the best we can do.  Also,  some
> more testers will be able to try it out and report any problems....

Mime
View raw message