[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] Move library version to svn_config.

From: Scott Lamb <slamb_at_slamb.org>
Date: 2002-08-07 14:41:07 CEST

Greg Stein wrote:
> On Tue, Aug 06, 2002 at 06:26:11PM -0500, Scott Lamb wrote:
>>Question: why are the build.conf and build-outputs.mk filenames handled
>>the way they are? They're passed through several levels of Python code
>>but hardcoded in the end in gen-make.py or autogen.sh. I tried to match
>>it with the svn-version.h filename, but I confess I don't see the point.
> Hard-coded? gen-make.py only hardcodes the -outputs.mk suffix. Is that what
> you're referring to? As to why... well, why not? :-)
> autogen.sh has to hard-code something. It's the guy that gets the system set
> up. I don't see why it *shouldn't* hardcode build.conf.
> I gotta confess that I don't quite understand what you're driving at here.
> Cheers,
> -g

Yeah, that's what I'm referring to. gen-make.py hardcodes `basename
$buildconf .conf`-outputs.mk and autogen.sh hardcodes build.conf. It
just seemed funny that they were made mostly-configurable in
gen-make.py, gen_base.py, and gen_make.py, when apparently no one uses
it with anything other than build.conf. Not a huge deal.

Scott Lamb
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 7 14:41:47 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.