Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 6 Jun 2001 15:49:18 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: point to FAQs [WAS: Re: getopts....] Message-ID: <20010606154918.B17836@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3B1C8C03 DOT 23629 DOT 92EA659 AT localhost> <4A256A62 DOT 000952F0 DOT 00 AT bqlho_nts5 DOT boq DOT com DOT au> <3B1C8C03 DOT 23629 DOT 92EA659 AT localhost> <4 DOT 3 DOT 1 DOT 2 DOT 20010605110618 DOT 020d0a80 AT pop DOT ma DOT ultranet DOT com> <3B1CFB45 DOT 931B13F2 AT yahoo DOT com> <4 DOT 3 DOT 1 DOT 2 DOT 20010605114146 DOT 0219b9f8 AT pop DOT ma DOT ultranet DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <4.3.1.2.20010605114146.0219b9f8@pop.ma.ultranet.com>; from lhall@rfk.com on Tue, Jun 05, 2001 at 11:43:47AM -0400 On Tue, Jun 05, 2001 at 11:43:47AM -0400, Larry Hall (RFK Partners, Inc) wrote: >At 11:31 AM 6/5/2001, Earnie Boyd wrote: >>"Larry Hall (RFK Partners, Inc)" wrote: >> > >> > No, I don't think so. I really haven't seen this asked frequently and >> > I also feel uncomfortable with the idea that the Cygwin FAQ provide >> > answers that more appropriately belong in other packages' FAQs. It would >> > be nice if the Cygwin FAQ could provide "one-stop shopping" for every >> > issue but then I think it would become so difficult to navigate and use >> > that it would defeat its purpose. People wanting to know what the >> > possibilities are for building ash with this option or gcc with that >> > should really look to the sites and lists that support those packages. >> > In particular, this query and response may be a good addition to the ash >> > site/FAQ. I do think it would be worthwhile and appropriate for the >> > Cygwin FAQ to point to FAQs of packages it contains though. >> > >> >>This sounds nice but outdates quickly. A better approach would be to >>add pointers to package FAQs in the documentation for that package. >>Then it wouldn't be up to David to keep abreast of when a pointer >>changes. It would be spread amongst the many (HA!:) ported package >>maintainers. > > > >Good point. That's the goal I had in mind. > >Thanks for the clarification. I will always resist FAQ entries that essentially say "Please use your brain." It only takes a little bit of effort to download the ash sources and figure this out for yourself. Since this is a very nonstandard use of the tools, I am not going to sanction the inclusion of anything like this in the FAQ. The other extremely obvious choice is to use /bin/bash. We want to the FAQ to be useful. If it grows to 197MB then it will not be useful. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple