Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 8 Sep 2002 23:47:19 -0700
From: Aaron Bannert <aaron@clove.org>
To: dev@httpd.apache.org
Cc: dev@apr.apache.org
Subject: Re: Is it time to split the APR/HTTPD releases ?
Message-ID: <20020909064719.GS5445@clove.org>
Mail-Followup-To: Aaron Bannert <aaron@clove.org>, dev@httpd.apache.org,
	dev@apr.apache.org
References: <3D7C1753.1070606@apache.org>
 <Pine.LNX.4.21.0209082348470.25958-100000@shell.ntrnet.net>
 <20020908233735.A31743@lyra.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020908233735.A31743@lyra.org>
User-Agent: Mutt/1.4i

[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