Received: from hotzsun.jpl.nasa.gov (root@hotzsun.jpl.nasa.gov [137.78.218.98]) by hub.org (8.8.8/8.7.5) with ESMTP id UAA18515 for ; Tue, 25 Aug 1998 20:18:31 -0400 (EDT) Received: from [137.78.218.94] (hotzmac [137.78.218.94]) by hotzsun.jpl.nasa.gov (8.7.6/8.7.3) with ESMTP id RAA14157; Tue, 25 Aug 1998 17:14:06 -0700 (PDT) X-Sender: hotzmail@hotzsun.jpl.nasa.gov Message-Id: In-Reply-To: <199808250626.CAA07641@candle.pha.pa.us> References: <35E25602.1CBB6D5F@alumni.caltech.edu> from "Thomas G. Lockhart" at "Aug 25, 1998 6:13:22 am" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 25 Aug 1998 17:13:34 -0700 To: Bruce Momjian , lockhart@alumni.caltech.edu (Thomas G. Lockhart) From: "Henry B. Hotz" Subject: Re: [HACKERS] Open 6.4 items Cc: hackers@postgreSQL.org At 11:26 PM -0700 8/24/98, Bruce Momjian wrote: >> That is possible. But why are fundamental things like installation >> instructions or release notes better left as flat files? Can't quite see > >OK. As long as we can generate flat too for those that can't use fancy >stuff. Certainly it is better than flat files if both are available for >novices trying to get started. > My $.02. Having just built a new server I like the fact that most packages (gcc, apache, perl) have a top-level INSTALL and README file. They are flat files so you can look at them before you have installed anything. I like the convention. More specifically you shouldn't have to install anything to read the INSTALL file. Signature failed Preliminary Design Review. Feasibility of a new signature is currently being evaluated. h.b.hotz@jpl.nasa.gov, or hbhotz@oxy.edu