Received: from localhost (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203])
	by hub.org (8.9.3/8.9.3) with ESMTP id QAA13346;
	Sat, 17 Jul 1999 16:53:39 -0400 (EDT)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1])
	by localhost (8.8.7/8.8.7) with ESMTP id UAA06175;
	Sat, 17 Jul 1999 20:54:25 GMT
Sender: lockhart@hub.org
Message-ID: <3790ED81.B9F38C0D@alumni.caltech.edu>
Date: Sat, 17 Jul 1999 20:54:25 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Postgres Documentation List <docs@postgreSQL.org>,
	Postgres Hackers List <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Merging old man pages
References: <20015.932232121@sss.pgh.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> OK, let me get this straight: man pages will no longer be in the CVS
> tree because they will no longer be original files, but they will be
> part of the standard distribution as derived files, right?

Yes. Well, at least, maybe, sort of...

As is the case with the other (html) docs, I'm planning on putting a
man tarball into the distribution. Up to now, the easiest way to do
that is to put the tarball into cvs, but I'm open to other
suggestions.

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? 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.

                  - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California