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: Wed, 16 Jul 2003 01:43:07 -0400 From: Christopher Faylor Subject: Re: Ideas re problem reporting In-reply-to: <1058333460.3403.303.camel@localhost> To: cygwin AT cygwin DOT com Reply-to: cygwin AT cygwin DOT com Mail-followup-to: cygwin AT cygwin DOT com Message-id: <20030716054307.GC3817@redhat.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.4.1i References: <20030716002142 DOT E1F2434381 AT nevin DOT research DOT canon DOT com DOT au> <20030716033302 DOT GA6050 AT redhat DOT com> <1058333460 DOT 3403 DOT 303 DOT camel AT localhost> On Wed, Jul 16, 2003 at 03:31:00PM +1000, Robert Collins wrote: >On Wed, 2003-07-16 at 13:33, Christopher Faylor wrote: > >> 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. > >I've seen at least one script that (badly) reverse engineered setup's db >files and attempts to create compatible ones. Really? Where was this? We should certainly be on the lookout for this. 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/