Return-Path: X-Original-To: apmail-apr-dev-archive@www.apache.org Delivered-To: apmail-apr-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 02CA110E78 for ; Tue, 29 Oct 2013 11:20:52 +0000 (UTC) Received: (qmail 4502 invoked by uid 500); 29 Oct 2013 11:20:48 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 2111 invoked by uid 500); 29 Oct 2013 11:20:41 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 1002 invoked by uid 99); 29 Oct 2013 11:20:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Oct 2013 11:20:39 +0000 X-ASF-Spam-Status: No, hits=2.7 required=5.0 tests=HTML_MESSAGE,MISSING_HEADERS,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of trawick@gmail.com designates 209.85.217.182 as permitted sender) Received: from [209.85.217.182] (HELO mail-lb0-f182.google.com) (209.85.217.182) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Oct 2013 11:20:35 +0000 Received: by mail-lb0-f182.google.com with SMTP id w6so4000044lbh.27 for ; Tue, 29 Oct 2013 04:20:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=Z9+ZRS0auGVByN1K5hRJxWJ1a/6Jva7X2xlCG+8d8W8=; b=iH1sNaqLvZsJScsU6FZAdV43SyZjBeawVq+JbbvE6LLI4K1oqXgeTjugH0KlJ0oT0M b4ispsLrPdtl84gWQfqUNUdo63yKKEQfiEQ9KZfG5gFnrjPaE90ruF3i1K8CwudOYClX gVbBoXtlcD4LAqR6GzoTBJEzTPpAvkUcDjzZg7ZsT1opIYQ1roPsJ9Ne7tXU5UFQOpg1 AEgrDr0saX21cczMXfryHPBj3Gpze0MCcC9wjfCd/RJ0UtaoaO6qHcucR8JhMtQRO32J 1O3Ua0NV9sP0sUqQa8gRTOVBnpsbRsvmQbp5Z3iyPsZm2U0+IWNVMu5sIUflFA7tHWhQ Zkmg== MIME-Version: 1.0 X-Received: by 10.112.11.20 with SMTP id m20mr596234lbb.56.1383045614028; Tue, 29 Oct 2013 04:20:14 -0700 (PDT) Received: by 10.114.187.71 with HTTP; Tue, 29 Oct 2013 04:20:13 -0700 (PDT) In-Reply-To: References: <5260A63B.20301@gknw.net> <5262C226.4020509@gknw.net> <526E95EA.6020304@gknw.net> <20131028155411.0fc3ea12@hub> <20131028163753.55c73a47@hub> Date: Tue, 29 Oct 2013 07:20:13 -0400 Message-ID: Subject: Re: Timetable for APR 1.5 release? From: Jeff Trawick Cc: APR Developer List Content-Type: multipart/alternative; boundary=001a1133eb74884d4604e9df667d X-Virus-Checked: Checked by ClamAV on apache.org --001a1133eb74884d4604e9df667d Content-Type: text/plain; charset=ISO-8859-1 On Tue, Oct 29, 2013 at 5:21 AM, Michael Felt wrote: > Just to verify what I should be testing - and - is it too late to get > something added for packaging? > > I assume that for httpd-2.4.X that should build with only apr-1.5.X > (preferred), or with apr-1.4.some-minimum + apr-util-1.5.X > httpd 2.4.next will require apr-1.5.x only if using the event MPM (I doubt that works on AIX anyway). But many if not most will be using the latest apr and apr-util. > > What I would like to add is the buildaix scripts - similar to what I did > for httpd, or at a minimum, the layout.AIX. > > As apr has compiler dependancies (if you change complier you must rebuild > apr) I would prefer to have the build script that changes the package name > dependent on the compiler. > > A nice start would be the AIX layout. > > michael@x054:[/data/prj/apache/apr/apr-1.5.x-save]jsvn diff config.layout > Index: config.layout > =================================================================== > Does this work with apr trunk? It needs to be committed there first, then to 1.5.x. > --- config.layout (revision 1536612) > +++ config.layout (working copy) > @@ -229,3 +229,26 @@ > infodir: ${exec_prefix}/share/info > libsuffix: -${APR_MAJOR_VERSION} > > + > +# AIX layout > + > + prefix: /opt > + exec_prefix: /opt > + datadir: /var/apr > + localstatedir: /var > + sysconfdir: ${localstatedir}/apr/etc > + mandir: /usr/share/man > + bindir: ${exec_prefix}/bin > + sbindir: ${exec_prefix}/sbin > + includedir: ${exec_prefix}/include > + libdir: ${exec_prefix}/lib > + libexecdir: ${exec_prefix}/libexec > + errordir: ${datadir}/error > + iconsdir: ${datadir}/icons > + htdocsdir: ${datadir}/htdocs > + manualdir: ${datadir}/manual > + runtimedir: ${localstatedir}/run > + logfiledir: ${localstatedir}/logs > + proxycachedir: ${localstatedir}/proxy > + installbuilddir: ${localstatedir}/build > + > > Is it necessary to control all of these from the layout? There are significantly more settings, generally httpd-specific, than the other layouts have. proxycachedir? That sounds like Apache 1.3 to me. What uses that? > > > > On Mon, Oct 28, 2013 at 10:37 PM, William A. Rowe Jr. > wrote: > >> On Mon, 28 Oct 2013 16:58:45 -0400 >> Jeff Trawick wrote: >> >> > On Mon, Oct 28, 2013 at 4:54 PM, William A. Rowe Jr. >> > wrote: >> > >> > > On Mon, 28 Oct 2013 13:01:09 -0400 >> > > Jeff Trawick wrote: >> > > >> > > > On Mon, Oct 28, 2013 at 12:50 PM, Gregg Smith >> > > > wrote: >> > > > >> > > > > Just a note, >> > > > > >> > > > > >> > > > > On 10/19/2013 10:32 AM, Gregg Smith wrote: >> > > > > >> > > > >> On 10/19/2013 7:26 AM, Jeff Trawick wrote: >> > > > >> >> > > > >>> On Thu, Oct 17, 2013 at 11:08 PM, Gregg Smith > > > > >>> > wrote: >> > > > >>> >> > > > >>> I'd like to first rid the 1.5 traditional Windows build >> > > > >>> of the Release9x & Debug9x targets. Anyone against this? >> > > > >>> >> > > > >>> >> > > > >>> no concerns here; is there code that can get deleted too? >> > > > >>> >> > > > >> >> > > > >> probably, I would assume so, I haven't ran it down that far >> > > > >> yet. >> > > > >> >> > > > > >> > > > > I did not do this after all nor do I think I am brave enough to. >> > > > > >> > > > > apr_escape, testescape and gen_test_char were added into the >> > > > > build with r1534053. >> > > > > .mak/.dep files were added in r1534516. >> > > > > >> > > > > We should be ready to go on the Windows side now. >> > > >> > > So, given that 1.5 remains compatible with 1.4... but projects which >> > > build APR themselves will have to adapt to the new gen_test_char or >> > > we need to make the suggested change, let's just take the httpd >> > > example. >> > > >> > > Does it make more sense for httpd 2.2 Makefile.win to detect the >> > > presence of gen_test_char and build it when encountered, or does it >> > > make more sense to compile-link-invoke gen_test_char.c? I'm happy >> > > to make the respective change later tonight or tomorrow, based on >> > > consensus. >> > > >> > > >> > Is the Windows build interface of apr 1.5.x different such that >> > httpd's Makefile.win would care? >> > >> > httpd itself doesn't use apr escape and shouldn't care that apr >> > happens to have a build utility of the same name as one of its own >> > (or something is borked). >> >> The httpd 2.2 Makefile.win build invokes the pcre, expat, apr, apr-iconv >> and apr-util builds project-by-project, it doesn't use any corresponding >> top-level build mechanics. This was one aspect that was greatly improved >> by moving to the httpd-2.4 model. >> >> If httpd doesn't pre-build gen_test_char before apr.mak, then the apr >> build will fail, unless we nest the new gen_test_char pre-build. >> >> I think the better solution for a one-source file, source generation >> app is to embed that build into the [lib]apr.dsp/mak files for now. >> But as an alternative, we can teach httpd 2.2 Makefile.win to anticipate >> this requirement if that project is present. That would mean that 1.5 >> apr wouldn't build with older httpd 2.2 releases, only the next release >> onwards. >> >> > -- Born in Roswell... married an alien... http://emptyhammock.com/ --001a1133eb74884d4604e9df667d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

= On Tue, Oct 29, 2013 at 5:21 AM, Michael Felt <mamfelt@gmail.com> wrote:
Just to= verify what I should be testing - and - is it too late to get something ad= ded for packaging?

I assume that for httpd-2.4.X that should build with only apr-1.5= .X (preferred), or with apr-1.4.some-minimum + apr-util-1.5.X

httpd 2.4.next will require = apr-1.5.x only if using the event MPM (I doubt that works on AIX anyway).

But many if not most will be using the latest apr and a= pr-util.
=A0

What I would like to add is the buildaix scripts - similar to wha= t I did for httpd, or at a minimum, the layout.AIX.

As apr has= compiler dependancies (if you change complier you must rebuild apr) I woul= d prefer to have the build script that changes the package name dependent o= n the compiler.

A nice start would be the AIX layout.

michael@x054:[/data/= prj/apache/apr/apr-1.5.x-save]jsvn diff config.layout
Index: config.layo= ut
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Does this work with apr trunk? =A0It= needs to be committed there first, then to 1.5.x.
=A0
--- config.layout=A0=A0=A0=A0=A0=A0 (revision 1536612)
+++ config.layout= =A0=A0=A0=A0=A0=A0 (working copy)
@@ -229,3 +229,26 @@
=A0=A0=A0=A0 i= nfodir:=A0=A0=A0=A0=A0=A0 ${exec_prefix}/share/info
=A0=A0=A0=A0 libsuff= ix:=A0=A0=A0 -${APR_MAJOR_VERSION}
=A0</Layout>
+
+# AIX layout
+<Layout AIX>
+=A0=A0=A0 prefix:=A0=A0=A0=A0= =A0=A0=A0 /opt
+=A0=A0=A0 exec_prefix:=A0=A0 /opt
+=A0=A0=A0 datadir:= =A0=A0=A0=A0=A0=A0 /var/apr
+=A0=A0=A0 localstatedir: /var
+=A0=A0=A0= sysconfdir:=A0=A0=A0 ${localstatedir}/apr/etc
+=A0=A0=A0 mandir:=A0=A0= =A0=A0=A0=A0=A0 /usr/share/man
+=A0=A0=A0 bindir:=A0=A0=A0=A0=A0=A0=A0 ${exec_prefix}/bin
+=A0=A0=A0 sb= indir:=A0=A0=A0=A0=A0=A0 ${exec_prefix}/sbin
+=A0=A0=A0 includedir:=A0= =A0=A0 ${exec_prefix}/include
+=A0=A0=A0 libdir:=A0=A0=A0=A0=A0=A0=A0 ${= exec_prefix}/lib
+=A0=A0=A0 libexecdir:=A0=A0=A0 ${exec_prefix}/libexec<= br>+=A0=A0=A0 errordir:=A0=A0=A0=A0=A0 ${datadir}/error
+=A0=A0=A0 iconsdir:=A0=A0=A0=A0=A0 ${datadir}/icons
+=A0=A0=A0 htdocsdi= r:=A0=A0=A0=A0 ${datadir}/htdocs
+=A0=A0=A0 manualdir:=A0=A0=A0=A0 ${dat= adir}/manual
+=A0=A0=A0 runtimedir:=A0=A0=A0 ${localstatedir}/run
+= =A0=A0=A0 logfiledir:=A0=A0=A0 ${localstatedir}/logs
+=A0=A0=A0 proxycac= hedir: ${localstatedir}/proxy
+=A0=A0=A0 installbuilddir: ${localstatedir}/build
+</Layout>
<= br>
Is it necessary to control all of these from the= layout? =A0There are significantly more settings, generally httpd-specific= , than the other layouts have.

proxycachedir? =A0That sounds like Apache 1.3 to me. = =A0What uses that?





On Mon, Oct 28, 2013 at 10:37 PM, = William A. Rowe Jr. <wrowe@rowe-clan.net> wrote:
On Mon, 28 Oct 2013 16:58:45 -0400
Jeff Trawick <trawick@gmail.com> wrote:

> On Mon, Oct 28, 2013 at 4:54 PM, William A. Rowe Jr.
> <wrowe@row= e-clan.net>wrote:
>
> > On Mon, 28 Oct 2013 13:01:09 -0400
> > Jeff Trawick <trawick@gmail.com> wrote:
> >
> > > On Mon, Oct 28, 2013 at 12:50 PM, Gregg Smith <gls@gknw.net>
> > > wrote:
> > >
> > > > Just a note,
> > > >
> > > >
> > > > On 10/19/2013 10:32 AM, Gregg Smith wrote:
> > > >
> > > >> On 10/19/2013 7:26 AM, Jeff Trawick wrote:
> > > >>
> > > >>> On Thu, Oct 17, 2013 at 11:08 PM, Gregg Smith &= lt;gls@gknw.net
> > > >>> <mailto: gls@gknw.net>> wrote:
> > > >>>
> > > >>> =A0 =A0 I'd like to first rid the 1.5 tradi= tional Windows build
> > > >>> of the Release9x & Debug9x targets. Anyone = against this?
> > > >>>
> > > >>>
> > > >>> no concerns here; is there code that can get de= leted too?
> > > >>>
> > > >>
> > > >> probably, I would assume so, I haven't ran it d= own that far
> > > >> yet.
> > > >>
> > > >
> > > > I did not do this after all nor do I think I am brave e= nough to.
> > > >
> > > > apr_escape, testescape and gen_test_char were added int= o the
> > > > build with r1534053.
> > > > .mak/.dep files were added in r1534516.
> > > >
> > > > We should be ready to go on the Windows side now.
> >
> > So, given that 1.5 remains compatible with 1.4... but projects wh= ich
> > build APR themselves will have to adapt to the new gen_test_char = or
> > we need to make the suggested change, let's just take the htt= pd
> > example.
> >
> > Does it make more sense for httpd 2.2 Makefile.win to detect the<= br> > > presence of gen_test_char and build it when encountered, or does = it
> > make more sense to compile-link-invoke gen_test_char.c? =A0I'= m happy
> > to make the respective change later tonight or tomorrow, based on=
> > consensus.
> >
> >
> Is the Windows build interface of apr 1.5.x different such that
> httpd's Makefile.win would care?
>
> httpd itself doesn't use apr escape and shouldn't care that ap= r
> happens to have a build utility of the same name as one of its own
> (or something is borked).

The httpd 2.2 Makefile.win build invokes the pcre, expat, apr, = apr-iconv
and apr-util builds project-by-project, it doesn't use any correspondin= g
top-level build mechanics. =A0This was one aspect that was greatly improved=
by moving to the httpd-2.4 model.

If httpd doesn't pre-build gen_test_char before apr.mak, then the apr build will fail, unless we nest the new gen_test_char pre-build.

I think the better solution for a one-source file, source generation
app is to embed that build into the [lib]apr.dsp/mak files for now.
But as an alternative, we can teach httpd 2.2 Makefile.win to anticipate this requirement if that project is present. =A0That would mean that 1.5 apr wouldn't build with older httpd 2.2 releases, only the next release=
onwards.





--
= Born in Roswell... married an alien...
http://emptyhammock.com/
--001a1133eb74884d4604e9df667d--