Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Tue, 15 Jul 2003 23:33:02 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Ideas re problem reporting Message-ID: <20030716033302.GA6050@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20030716002142 DOT E1F2434381 AT nevin DOT research DOT canon DOT com DOT au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030716002142.E1F2434381@nevin.research.canon.com.au> User-Agent: Mutt/1.4.1i On Wed, Jul 16, 2003 at 10:21:42AM +1000, luke DOT kendall AT cisra DOT canon DOT com DOT au wrote: >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. cygcheck -rsv (or cygcheck -c) already implies this. If the output from cycheck doesn't include package information, then the packages weren't installed via setup.exe. cgf -- 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/