Thread: Re: [COMMITTERS] pgsql-server/doc/src/sgml Makefile
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
Bruce Momjian wrote: > 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. Please do not automatically overwrite files that are in CVS. That will lead to trouble. An alternative, which is actually in quite common use, is to simply provide a file README.cvs that explains various things about dealing with a CVS check out tree. When you make a tarball, you simply delete the file.
Peter Eisentraut wrote: > Bruce Momjian wrote: > > 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. > > Please do not automatically overwrite files that are in CVS. That will > lead to trouble. An alternative, which is actually in quite common > use, is to simply provide a file README.cvs that explains various > things about dealing with a CVS check out tree. When you make a > tarball, you simply delete the file. OK, I have removed HISTORY and INSTALL from CVS, and added a README.CVS which contains URL's to that content. Marc, would you modify your tar build script to remove README.CVS from the tar file? -- 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
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> OK, I have removed HISTORY and INSTALL from CVS, and added a README.CVS
> which contains URL's to that content.
> Marc, would you modify your tar build script to remove README.CVS from
> the tar file?
Sounds good, but are we all on the same page here? Does this apply only
to CVS HEAD, or also in the 7.4 and 7.3 branches? (I assume we are not
planning any further releases before 7.3.)
regards, tom lane
Tom Lane wrote: > Bruce Momjian <pgman@candle.pha.pa.us> writes: > > OK, I have removed HISTORY and INSTALL from CVS, and added a README.CVS > > which contains URL's to that content. > > > Marc, would you modify your tar build script to remove README.CVS from > > the tar file? > > Sounds good, but are we all on the same page here? Does this apply only > to CVS HEAD, or also in the 7.4 and 7.3 branches? (I assume we are not > planning any further releases before 7.3.) I have done this for 7.4.X and HEAD. I didn't touch 7.3. -- 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