httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Reid" <>
Subject Re: Pause to Consider
Date Thu, 25 Nov 1999 15:55:46 GMT
Maybe then we should focus on the end result?  We all know what we want so
we just need tools that deliver the ideal?

I don't really mind I just wanted to voice my concerns, which I've done, so
full speed ahead Capt Ahab!

----- Original Message -----
From: Jim Jagielski <>
To: <>
Sent: 25 November 1999 15:48
Subject: Re: Pause to Consider

> Ralf S. Engelschall wrote:
> >
> > Yes, how do you plan to address the apxs issue? That is, how to you plan
> > integrate your Autoconf approach with the functionality of the old
> > modules externally [via apxs]"? Currently it looks to me you've still
> > thought about this, because you have direct references between your
> > stuff and the modules (you do a "cat *.m4" mainly).  This breaks for
> > which should be configured and built externally.
> >
> I think that maintaining 'apxs' "as in" should NOT be a goal. Everything
> is up for grabs. There might be a better way than adjusting the entire
> build sequence to maintain apxs. I say we maintain the end-result of
> what apxs accomplishes, but leave apxs out of the picture.
> --
>    Jim Jagielski   [|]   [|]
>                 "Are you suggesting coconuts migrate??"

View raw message