Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Date: Sat, 16 Dec 2000 13:17:27 -0800
From: Greg Stein <gstein@lyra.org>
To: dev@apr.apache.org
Subject: Re: *.exports in distro bundle
Message-ID: <20001216131727.F30887@lyra.org>
Mail-Followup-To: dev@apr.apache.org
References: <Pine.LNX.4.30.0012161905150.5646-100000@rossini.schumann.cx>
 <Pine.LNX.4.21.0012161020160.22699-100000@koj.rkbloom.net>
 <20001216123654.B30887@lyra.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <20001216123654.B30887@lyra.org>;
 from gstein@lyra.org on Sat, Dec 16, 2000 at 12:36:55PM -0800

On Sat, Dec 16, 2000 at 12:36:55PM -0800, Greg Stein wrote:
> On Sat, Dec 16, 2000 at 10:28:07AM -0800, rbb@covalent.net wrote:
>...
> > When I originally wrote the buildexports stuff, we didn't require Perl to
> > build Apache, because that file could be generated once and just bundled
> > with Apache.  With the move to create those files during the build steps,
> > we now require Perl just to build.  I think the best solution is to move
> > that step back to the buildconf script, because that allows us to bundle
> > these files with the packages.
> 
> We can make *.exports at release-time and bundle them into the distro. The
> files won't be regenerated since they already exists.
>...
> Keeping it in the make step is important for the developers. When the
> headers change, it is nice to have the exports automatically updated. When
> Jeff took out some of the address lookup stuff, it got rebuilt for me and
> everything was happy. No re-running buildconf just to get rid of it.

I just thought of something. Nothing precludes us from building *.exports in
buildconf (e.g. in prep for a release). The make step remains for developers
when they update the header files.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/