From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Lockhart <lockhart@alumni.caltech.edu>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: The Hermit Hacker <scrappy@hub.org>
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: v7.1 beta 1 ...packaged, finally ...
Date: Fri, 08 Dec 2000 00:55:21 -0500
Message-ID: <29512.976254921@sss.pgh.pa.us> (raw)
In-Reply-To: <3A30654A.2095B859@alumni.caltech.edu>
References: <Pine.LNX.4.30.0012072201340.780-100000@peter.localdomain>
<17344.976225439@sss.pgh.pa.us>
<3A30654A.2095B859@alumni.caltech.edu>
Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
> [ various good reasons ]
> 3) We put the docs into cvs, but the jade/docbook output did not have
> predictable file names. So each release would require wiping the output
> docs and somehow guessing which files were obsolete and which were new.
That's something that's annoyed me for a good while in a different
context, namely that URLs for particular pages of the docs on
postgresql.org aren't stable. (Well, maybe they are? but foo58342.htm
doesn't give one a warm feeling about it. chap3sec7.htm would look
a lot better.)
Is there any prospect of making the output filenames more predictable?
Who should I annoy about it?
> I think that *requiring* that the html docs be built in place to effect
> a release is an extra toolset burden that we should not accept.
Agreed on that one...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, lockhart@alumni.caltech.edu, peter_e@gmx.net, scrappy@hub.org, pgsql-hackers@postgresql.org
Subject: Re: v7.1 beta 1 ...packaged, finally ...
In-Reply-To: <29512.976254921@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox