To: Peter Eisentraut <peter_e@gmx.net>
Cc: Rod Taylor <pg@rbt.ca>, Kemin Zhou <kemin.zhou@ferring.com>,
	pgsql-sql@postgresql.org
Subject: Re: Server Side C programming Environment Set up 
In-reply-to: <200404231045.43614.peter_e@gmx.net> 
References: <4086B601.3030108@ferring.com> <1082642297.91360.9.camel@jester>
	<7546.1082650023@sss.pgh.pa.us>
	<200404231045.43614.peter_e@gmx.net>
Comments: In-reply-to Peter Eisentraut <peter_e@gmx.net>
	message dated "Fri, 23 Apr 2004 10:45:43 +0200"
Date: Fri, 23 Apr 2004 08:01:31 -0400
Message-ID: <20636.1082721691@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Peter Eisentraut <peter_e@gmx.net> writes:
> I'd be happy to write more documentation, howtos, or scripts and tools that 
> enable users to set up a proper build system, but I don't think it's our 
> business to try to write our own build system framework.

Any build framework is going to have limitations, obviously, and it
would be bad to design things to prevent subprojects from having their
own.  But I think that is no argument for not having a build framework
at all.  If we try to go that route, we'll be killing a lot of useful
code that isn't quite valuable enough (in isolation) for people to
expend the work to create their own build system for.

Even more to the point, we've already *got* a build framework, which by
demonstration works for many of the bits of code that we are talking
about spinning off.  What we have to do is adjust it so it still works
for them after they're spun off.  It seems silly to abandon the
not-trivial work you and other people have already put into the contrib
build system; and also silly to expect gborg projects to individually
adapt it to their needs.

			regards, tom lane