point to FAQs [WAS: Re: getopts....]
Wed Jun 6 12:49:00 GMT 2001
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
>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.
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin