Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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: Tue, 3 Aug 2004 12:38:41 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: how to check what cygwin packages are installed on the system ?
Message-ID: <20040803163841.GA20692@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <F67AB1DD14544242BE5BFE94F5939175B7F983 AT E2KMEMMCS1 DOT ftbco DOT ftn DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F67AB1DD14544242BE5BFE94F5939175B7F983@E2KMEMMCS1.ftbco.ftn.com>
User-Agent: Mutt/1.4.1i

On Tue, Aug 03, 2004 at 10:58:48AM -0500, DePriest, Jason R. wrote:
>On Tuesday, August 03, 2004 10:45 AM, Robin Bowes wrote
>
>> On Tue, August 3, 2004 16:19, Andrew DeFaria said:
>>> Christopher Faylor wrote:
>>>> 
>>>> And you would do that rather than use the tool designed for
>>>> providing 
>>>> the information, because...?
>>> 
>>> To answer the question: "Which package brought in this file?" as in:
>>> 
>>> 
>>> $ cd /etc/setup
>>> $ str=gcc.exe
>>> $ for pkg in *.gz; do
>>> 
>>>> zcat $pkg | grep -q $str if [ $? -eq 0 ]; then echo $str appears in
>>>> $pkg fi done 
>> 
>> Or:
>> 
>> $ cygcheck -f /usr/bin/gcc.exe
>> gcc-3.3.1-3
>> 
>> R.
>> --
>> http://robinbowes.com
>
>$ cygcheck -f /etc/inetd.conf
><nothing>
>
>$ for pkg in *.gz; do zcat $pkg | grep -q "inetd.conf"; if [ $? -eq 0 ];
>then echo $str appears in $pkg; fi; done
>appears in xinetd.lst.gz
>
>cygcheck -f works for some files apparently, but not all.

Yeah, that's clearly a good reason *not* to use cygcheck at all and to
just write your own shell script instead.

In fact, the next time someone finds a bug in the cygwin DLL, I'd suggest
just writing all of cygwin's functionality as a shell script, just to
be safe.

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/