Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA04523; Fri, 22 Jan 93 09:22:51 -0800
Date: Fri, 22 Jan 93 09:22:51 -0800
Message-Id: <9301221722.AA04523@postgres.Berkeley.EDU>
From: witr@rwwa.COM
Subject: Concern about new building environment
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
Content-Type: text
Content-Length: 1128

I am greatly concerned (perhaps wrongly) that the upcomming release's
use of a new make will *reduce* rather than *increase* portability.
Having just been through a rather painfull yet successfull port to
SVR4, I am wary of any potential for *increased* non-portability of
the postgres codebase.

Thus:

1) Will the new make environment (plus any ancillary tools) be
distributed *with* postgres?

2) If not, are these tools readily (and freely) available, and if so
where?

3) Is the new build going to assume that this new make is called
``make'' (and thus conflicting with whatever system-installed make
there is)?

4) How long is it likely to take to port the new make, before I can
even begin to port the new postgres?

5) Is the new build system going to correct unwarrented bsdocentric
assuptions, like: one always uses ranlib, each port always uses
exactly the same set of source files, shared objects end on .o, etc?

Thanks for any answers that can be supplied!

---
 Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
 R.W. Withrow Associates, 21 Railroad Ave, Swampscott MA 01907-1821 USA