[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apreq-dev
Subject:    Re: apreq release
From:       Steve Hay <steve.m.hay () googlemail ! com>
Date:       2016-11-17 13:09:58
Message-ID: CADED=K75Mq56R=1UhNXwRx3E4VX4aSbywi=uRUg1jLZFC+gXKQ () mail ! gmail ! com
[Download RAW message or body]

[Resending from an address that's actually subscribed to the lists...]

The current mod_perl release (2.0.10) is taken from trunk. (The
httpd24 branch was only for development work leading towards the
previous release (2.0.9), and is now obsolete.)

On 17 November 2016 at 09:03, Issac Goldstand <margol@beamartyr.net> wrote:
> Yes, if we go through with this.  The mod_apreq2 stuff is in httpd.
> However I just realized that although it's been in trunk for years now,
> it's never been backported to the 2.4.x branch.  I'm not sure why, and
> my google-fu isn't finding relevant discussion on dev@httpd.
> 
> When I initially took a look yesterday, I thought I'd looked at a 2.4
> release.  Can someone from the mod_perl dev community tell me if new
> releases (intended for httpd 2.4) come from trunk or from the httpd24
> branch?  If it's from the branch, then the apreq stuff could be moved to
> trunk (or a submodule, like Apache::Reload and friends if desired).  If
> trunk, then until mod_apreq is backported to httpd 2.4 (or httpd bumps
> versions and rebranches off of trunk)
> 
> 
> 
> On 11/16/2016 3:40 PM, Brian J. France wrote:
> > This is just merging the perl stuff into mod_perl, right?
> > 
> > Not merging mod_apreq2 and all the request cache/re-play bucket, POST reading, \
> > file uploading, etc stuff, right? 
> > I really don't want to have to include mod_perl so my C modules can read POST \
> > data and handle file uploads. 
> > Cheers,
> > 
> > Brian
> > 
> > 
> > > On Nov 16, 2016, at 4:42 AM, Issac Goldstand <margol@beamartyr.net> wrote:
> > > 
> > > Given that the C was (finally) merged into httpd years ago, and given
> > > that there are no proposed code changes, I'd say that's not such a bad
> > > idea...
> > > 
> > > I've become a bit rusty in Perl (and even with apreq) over the years,
> > > but IIRC, all of the Perl glue is in
> > > http://svn.apache.org/repos/asf/httpd/apreq/trunk/glue/perl/
> > > 
> > > I'll take a crack at seeing if I can fold it into mod_perl despite the rust.
> > > 
> > > 
> > > On 11/15/2016 2:45 PM, Andres Thomas Stivalet wrote:
> > > > Good news!! No idea why apreq hasn't just been merged into mod_perl
> > > > after all these years.
> > > > 
> > > > A+++
> > > > 
> > > > On Nov 15, 2016 3:27 AM, "Issac Goldstand" <margol@beamartyr.net
> > > > <mailto:margol@beamartyr.net>> wrote:
> > > > 
> > > > Hi all,
> > > > 
> > > > Someone (finally) noticed that apreq's test suite isn't compatible with
> > > > Apache 2.4 and requested a change.  Given that we haven't released an
> > > > updated apreq in nearly 6 years, I'm inclined to make/test the changes
> > > > to the test suite and immediately go to a release cycle.
> > > > 
> > > > Does anyone want time to add anything else to libapreq-2.14 before I
> > > > start tarring and voting (in the next few days, I hope)?
> > > > 
> > > > 
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
> > > > <mailto:dev-unsubscribe@perl.apache.org>
> > > > For additional commands, e-mail: dev-help@perl.apache.org
> > > > <mailto:dev-help@perl.apache.org>
> > > > 
> > > 
> > 
> 


[prev in list] [next in list] [prev in thread] [next in thread]