Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Wed, 16 Jul 2003 10:21:42 +1000 (EST)
From:	luke DOT kendall AT cisra DOT canon DOT com DOT au
Subject:	Ideas re problem reporting
To:	cygwin AT cygwin DOT com
In-Reply-To:	<o5bpcv867rhlo17vfmclotlv5nkr9f9m8f@4ax.com>
MIME-Version:	1.0
Message-Id:	<20030716002142.E1F2434381@nevin.research.canon.com.au>

On 22 May, Sam Edge wrote:
>  In addition, you are likely to get little help here with any problem 
>  unless you installed cygwin via the "official" setup.exe that you can 
>  get via the "Install Cygwin now" link on the http://www.cygwin.com/ 
>  web site. 

If this is a common occurrence (installing but bypassing setup.exe
somehow), then maybe it should finish by adding a registry entry to say
it did the install (and whether partial or full), so that problem
reports that include the system info would let you know this.

Perhaps even a bug reporting script that asked the questions you want
answered, and ran cygcheck etc. (basically, automating as much of the
http://cygwin.com/problems.html procedure as far as possible), might be
worthwhile.

If people think it's a good idea, I might have a go at one this weekend.

luke


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -