Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eB85tSZ39689 for ; Fri, 8 Dec 2000 00:55:29 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id eB85tMY29515; Fri, 8 Dec 2000 00:55:22 -0500 (EST) To: Thomas Lockhart cc: Peter Eisentraut , The Hermit Hacker , PostgreSQL Development Subject: Re: v7.1 beta 1 ...packaged, finally ... In-reply-to: <3A30654A.2095B859@alumni.caltech.edu> References: <17344.976225439@sss.pgh.pa.us> <3A30654A.2095B859@alumni.caltech.edu> Comments: In-reply-to Thomas Lockhart message dated "Fri, 08 Dec 2000 04:36:26 +0000" Date: Fri, 08 Dec 2000 00:55:21 -0500 Message-ID: <29512.976254921@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200012/319 X-Sequence-Number: 1817 Thomas Lockhart 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