From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200403091813.i29ID1427492@candle.pha.pa.us>
Subject: Re: [COMMITTERS] pgsql-server/doc/src/sgml Makefile
In-Reply-To: <27011.1078855252@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Date: Tue, 9 Mar 2004 13:13:01 -0500 (EST)
Cc: Peter Eisentraut <peter_e@gmx.net>,
	PostgreSQL-documentation <pgsql-docs@postgresql.org>,
	"Marc G. Fournier" <scrappy@hub.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> >> Peter Eisentraut <peter_e@gmx.net> writes:
> >>> A better approach for that would be to remove HISTORY from CVS and build 
> >>> it only when the release tarball is made.
> 
> > I think the only reason HISTORY and INSTALL are in CVS is because we
> > want people running CVS during beta to have changes docs and install
> > instructions that don't require them to pull down a new tarball each
> > time or read the docs via a web site.
> 
> That argument seems a bit silly for HISTORY, seeing that it's generally
> not up-to-date during beta testing.  As for INSTALL, those instructions
> don't change fast enough to surprise beta testers, so I'm not convinced
> about it either.

Actually, recent releases had a current HISTORY before beta started. 
However, if they are downloading the beta tarballs, the HISTORY/INSTALL
files are already generated.  It would only be useful for CVS pulls
during beta though.

One idea would be to replace file content with a single URL that points
to the development docs, then when the tarball is built, it can
overwrite those files.

Marc?

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073