On Wed, Jan 30, 2002 at 07:36:52AM -0800, Justin Erenkrantz wrote:
> On Tue, Jan 29, 2002 at 08:49:14PM -0500, Kevin Pilch-Bisson wrote:
> > I've been thinking a little about that recently. First a little context since
> > most of this happened on IRC. I was working on making it possible to use an
> > installed version of APR and Neon. My plan was to make a local copy of the
> > files we needed from APR to get our build system to work. Greg didn't like
> > that idea because he thought it would introduce version skew between the APR
> > version and our local copy. His idea was to have developer's (read those
> > running autogen.sh) require apr and neon in their tree, and have autogen.sh
> > copy those required files at its execution time. This would fix the version
> > skew problem. (This is also the reason the INSTALL doc says that autogen.sh
> > has the requirements, it used to, but we removed them when we went to allowing
> > separate installs).
>
> What files are we talking about requiring from APR to do a SVN build?
>
> If you just need PrintPath, I say to just add it to SVN. The actual
> PrintPath hasn't changed in about two years. If it magically changes
> and SVN needs that, someone can import the new version.
>
> If it's something other than that, you've got me scared. -- justin
>
We also used some autoconf macros, like APR_SUBDIR_CONFIG, and a couple of
others, which we basically copied whole-hog to SVN_SUBDIR_CONFIG. As I said
it's a lot of work for a little gain, since these aspects of APR have been
fairly stable for the months that they have been in svn. It just might be a
little more elegant.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson http://www.pilch-bisson.net
"Historically speaking, the presences of wheels in Unix
has never precluded their reinvention." - Larry Wall
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- application/pgp-signature attachment: stored
Received on Sat Oct 21 14:37:01 2006