Tom Lane wrote:
> >
> NAME="GENERATOR"
> CONTENT="Modular DocBook HTML Stylesheet Version 1.59">http://docbook.sourceforge.net/projects/dsssl/index.html
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> CONTENT="Modular DocBook HTML Stylesheet Version 1.59"> This qualifies as ancient. Newer versions are available from
> http://docbook.sourceforge.net/projects/dsssl/index.html
Okay. I see that both postgresql.org and Bruce are gen
Tom Lane wrote:
> Okay. I see that both postgresql.org and Bruce are generating the
> docs with
> Modular DocBook HTML Stylesheet Version 1.7
There is no version "1.7". This is in fact a bug; the correct version
number of the latest version (which is in use at postgresql.org) is
1.78.
>
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Also, I'm running openjade 1.3 on this machine, and as I recall it
>> was a serious pain in the arse to build. Is it worth worrying about
>> a newer version of that?
> Well, there is 1.3.2 now, but I can't tell you how easy or hard
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> CONTENT="Modular DocBook HTML Stylesheet Version 1.59">
> > This qualifies as ancient. Newer versions are available from
> > http://docbook.sourceforge.net/projects/dsssl/index.html
>
> Okay. I see that both
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> 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 ei
Bruce Momjian <[EMAIL PROTECTED]> writes:
> 2.8.5 is a development release of lynx, not a stable one:
> Lynx Version 2.8.5dev.16 (01 Jun 2003)
2.8.5rel1 is a release version that has been out for some time.
If you're running a development version, that's not my problem.
On Tue, 9 Mar 2004, 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.
>
> Marc?
Overwrite the files with ... ? The contents of the URL itself, pulled
down with
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
Marc G. Fournier wrote:
> On Tue, 9 Mar 2004, 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.
> >
> > Marc?
>
> Overwrite the files with ... ? The con
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > 2.8.5 is a development release of lynx, not a stable one:
> > Lynx Version 2.8.5dev.16 (01 Jun 2003)
>
> 2.8.5rel1 is a release version that has been out for some time.
> If you're running a development version, that's not my prob
On Tue, 9 Mar 2004, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> > On Tue, 9 Mar 2004, 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.
> > >
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
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> 2.8.5rel1 is a release version that has been out for some time.
>> If you're running a development version, that's not my problem.
> Well, looking at:
> http://lynx.browser.org/
> It mentions 2.8.3 as most current, and lists 2.8.
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> cp ~ftp/pub/dev/doc/postgres.tar.gz ~ftp/pub/dev/doc/man-7.4.tar.gz ../doc
That doesn't look right; for one thing you just made a postgres.tar.gz,
why would you overwrite it? Also see the business about whether
man.tar.gz has a version number.
> c
On Tue, 9 Mar 2004, Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > cp ~ftp/pub/dev/doc/postgres.tar.gz ~ftp/pub/dev/doc/man-7.4.tar.gz ../doc
>
> That doesn't look right; for one thing you just made a postgres.tar.gz,
> why would you overwrite it? Also see the business about
Tom Lane wrote:
> This gmake will leave some crud files that you don't want in the
> distro. Instead of 'cp' I'd suggest
> mv -f HISTORY INSTALL ../../..
> gmake clean
The "make dist" step will do its own cleaning.
---(end of broadcast)
Marc G. Fournier wrote:
> /usr/bin/cvs -d /cvsroot -q export -rHEAD pgsql
> cd pgsql
> ./configure
> cd doc/src
> gmake postgres.tar.gz
> mv postgres.tar.gz ..
> cp ~ftp/pub/dev/doc/postgres.tar.gz ~ftp/pub/dev/doc/man-7.4.tar.gz
> ../doc cd sgml
> gmake HISTORY INSTALL
> cp HISTORY INSTALL ../../.
On Tue, 9 Mar 2004, Peter Eisentraut wrote:
> Marc G. Fournier wrote:
> > /usr/bin/cvs -d /cvsroot -q export -rHEAD pgsql
> > cd pgsql
> > ./configure
> > cd doc/src
> > gmake postgres.tar.gz
> > mv postgres.tar.gz ..
> > cp ~ftp/pub/dev/doc/postgres.tar.gz ~ftp/pub/dev/doc/man-7.4.tar.gz
> > ../d
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Definitely open to suggestions on changing it ... I'm down to:
> cd doc/src
> gmake postgres.tar.gz
> mv postgres.tar.gz ..
> cp ~ftp/pub/dev/doc/man-7.4.tar.gz ../doc/man.tar.gz
On second look, isn't that copying the man tarball to the wrong
direc
On Tue, 9 Mar 2004, Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > Tom Lane wrote:
> > > This gmake will leave some crud files that you don't want in the
> > > distro. Instead of 'cp' I'd suggest
> > > mv -f HISTORY INSTALL ../../..
> > > gmake clean
> >
> > The "make dist" step will do it
On Tue, 9 Mar 2004, Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > Definitely open to suggestions on changing it ... I'm down to:
>
> > cd doc/src
> > gmake postgres.tar.gz
> > mv postgres.tar.gz ..
> > cp ~ftp/pub/dev/doc/man-7.4.tar.gz ../doc/man.tar.gz
>
> On second look,
On Tue, Mar 09, 2004 at 12:42:46 -0500,
Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
> 2.8.5 is a development release of lynx, not a stable one:
>
> Lynx Version 2.8.5dev.16 (01 Jun 2003)
>
> Do we want to standardize on a development version of some tools? It is
> only converting to text
On Tue, Mar 09, 2004 at 13:16:58 -0500,
Tom Lane <[EMAIL PROTECTED]> wrote:
>
> The other point is: how plausible is it really that someone testing CVS
> pulls would not find it convenient to read these docs from the website?
> They've got to have net access to do the pull in the first place.
I
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
> l
Bruce Momjian <[EMAIL PROTECTED]> 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?
26 matches
Mail list logo
