You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apr.apache.org by Aaron Bannert <aa...@clove.org> on 2002/09/09 08:47:19 UTC
Re: Is it time to split the APR/HTTPD releases ?
[sorry for the crosspost. I'm moving this branch of the conversation
to the dev@apr list]
On Sun, Sep 08, 2002 at 11:37:35PM -0700, Greg Stein wrote:
> The hardest problem is that httpd uses m4 files from APR. That means that
> APR *must* be present at srclib/apr/ when somebody runs 'buildconf'. After
> that, we *might* be able to toss srclib/apr, but I doubt it. I bet there are
> still quite a few paths into srclib/apr/build/ for Apache's build system.
> (but then again, I haven't looked... maybe when the FIND_APR work was done,
> everything was switched over to use the "found" APR rather than assuming
> that APR was placed into srclib)
This is why I really liked your apr-build project idea, so that we
could get all those useful .m4 files out into their own project to be
installed on any system that might need it. I have multiple projects
that right now do something lame like check apr_common.m4 into their
codebase so they can use the funtions in there, but it would be really
handy to just search for those in some standard locations the same way
we search for include files (for example).
-aaron
Re: Is it time to split the APR/HTTPD releases ?
Posted by Ian Holsman <ia...@apache.org>.
> On Mon, 2002-09-09 at 02:47, Aaron Bannert wrote:
>
>>[sorry for the crosspost. I'm moving this branch of the conversation
>>to the dev@apr list]
>>
>>
>>On Sun, Sep 08, 2002 at 11:37:35PM -0700, Greg Stein wrote:
>>
>>>The hardest problem is that httpd uses m4 files from APR. That means that
>>>APR *must* be present at srclib/apr/ when somebody runs 'buildconf'. After
>>>that, we *might* be able to toss srclib/apr, but I doubt it. I bet there are
>>>still quite a few paths into srclib/apr/build/ for Apache's build system.
>>>(but then again, I haven't looked... maybe when the FIND_APR work was done,
>>>everything was switched over to use the "found" APR rather than assuming
>>>that APR was placed into srclib)
>>
>>This is why I really liked your apr-build project idea, so that we
>>could get all those useful .m4 files out into their own project to be
>>installed on any system that might need it. I have multiple projects
>>that right now do something lame like check apr_common.m4 into their
>>codebase so they can use the funtions in there, but it would be really
>>handy to just search for those in some standard locations the same way
>>we search for include files (for example).
>>
couldn't this be done via the apr-config thingy we have ?
I kind of like the idea of having APR doing all the heavy m4 work, and
just get the 'users' of apr a config program to get the default values
>>-aaron
>
>
>
Re: Is it time to split the APR/HTTPD releases ?
Posted by Joshua Moore-Oliva <jo...@chatgris.com>.
I think that would be a great idea... As long as apr still came bundled
into apache, I woul dhave tons of uses for apr separate from apache.
Josh.
On Mon, 2002-09-09 at 02:47, Aaron Bannert wrote:
> [sorry for the crosspost. I'm moving this branch of the conversation
> to the dev@apr list]
>
>
> On Sun, Sep 08, 2002 at 11:37:35PM -0700, Greg Stein wrote:
> > The hardest problem is that httpd uses m4 files from APR. That means that
> > APR *must* be present at srclib/apr/ when somebody runs 'buildconf'. After
> > that, we *might* be able to toss srclib/apr, but I doubt it. I bet there are
> > still quite a few paths into srclib/apr/build/ for Apache's build system.
> > (but then again, I haven't looked... maybe when the FIND_APR work was done,
> > everything was switched over to use the "found" APR rather than assuming
> > that APR was placed into srclib)
>
> This is why I really liked your apr-build project idea, so that we
> could get all those useful .m4 files out into their own project to be
> installed on any system that might need it. I have multiple projects
> that right now do something lame like check apr_common.m4 into their
> codebase so they can use the funtions in there, but it would be really
> handy to just search for those in some standard locations the same way
> we search for include files (for example).
>
> -aaron
Re: Is it time to split the APR/HTTPD releases ?
Posted by Ask Bjoern Hansen <as...@develooper.com>.
On Sun, 8 Sep 2002, Aaron Bannert wrote:
> [sorry for the crosspost. I'm moving this branch of the conversation
> to the dev@apr list]
Except of course that we have ezmlm munge the reply-to headers so
you can't control such things...
- ask (who couldn't resist, sorry) :-)
--
ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
Re: Is it time to split the APR/HTTPD releases ?
Posted by Ask Bjoern Hansen <as...@develooper.com>.
On Sun, 8 Sep 2002, Aaron Bannert wrote:
> [sorry for the crosspost. I'm moving this branch of the conversation
> to the dev@apr list]
Except of course that we have ezmlm munge the reply-to headers so
you can't control such things...
- ask (who couldn't resist, sorry) :-)
--
ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();