Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > >> Peter Eisentraut <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
