Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2] (may be
	forged)) by hub.org (8.9.3/8.9.3) with ESMTP id RAA20692;
	Sat, 17 Jul 1999 17:48:31 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id RAA25678;
	Sat, 17 Jul 1999 17:47:22 -0400 (EDT)
To: Thomas Lockhart <lockhart@alumni.caltech.edu>
cc: Postgres Documentation List <docs@postgreSQL.org>,
	Postgres Hackers List <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Merging old man pages 
In-reply-to: Your message of Sat, 17 Jul 1999 20:54:25 +0000
	<3790ED81.B9F38C0D@alumni.caltech.edu>
Date: Sat, 17 Jul 1999 17:47:21 -0400
Message-ID: <25676.932248041@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
> Do I guess correctly that we currently generate our production
> releases by actually doing a cvs checkout and then a "mini-build" of
> the system to generate the yacc/bison derived files?

Right.

> If so, we could
> consider doing the same sort of thing for the html and man products,
> but it (probably) makes this packaging process more fragile.

Less fragile than doing it by hand ;-).  I'd say that's exactly the
way to proceed.

The shell script src/tools/release_prep contains the commands that
are executed (at hub.org) to prepare derived files for release.
Add whatever is needed to build the derived doc files, and we should
be set.

			regards, tom lane