Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm list-help: list-post: Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-apps AT sourceware DOT cygnus DOT com Message-ID: <3943B18A.8EB0E648@ece.gatech.edu> Date: Sun, 11 Jun 2000 11:34:34 -0400 From: "Charles S. Wilson" X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: cygapp CC: Chris Faylor Subject: Re: [FYI]: doc directory [was Re: [RFD]: Where to put the important README files?] References: <200006071636 DOT JAA09647 AT cygnus DOT com> <20000607154305 DOT F16163 AT cygnus DOT com> <39438E6B DOT 55D7915D AT vinschen DOT de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I will adhere to this standard with the packages on CygUtils, as I recompile/update them to become part of cygwin/latest/../extras or whatever. --Chuck Corinna Vinschen wrote: > > Chris Faylor wrote: > > On Wed, Jun 07, 2000 at 11:32:44AM -0500, Parker, Ron wrote: > > >Something like: > > > > > >* /usr/doc/Cygwin > > > > > >as a base directory for our documentation. Then later we could add: > > > > This idea gets my vote. > > FYI: I followed that suggestion for the latest inetutils-1.3.2-4 > package. The inetutils-1.3.2.README can now be found in > > /usr/doc/Cygwin > > Further releases of my various ports will always use > that directory as far as it's needed to provide a Cygwin > specific README for installation and/or configuration. > > Hope, other porters will use that in future, too. Only if > it's used by most packages, this will become a well-known > place for users to look for READMEs. > > Moreover we would have a new obligatory answer: > > Q: I don't know how to config that new blurb package? > A: RTF blurb.README in /usr/doc/Cygwin! > > Corinna