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 X-Server-Uuid: 0A4F2A26-D23B-4C5A-98BA-1B421465C24E content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: how to check what cygwin packages are installed on the system ? Date: Tue, 3 Aug 2004 11:42:49 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "DePriest, Jason R." To: cygwin AT cygwin DOT com X-OriginalArrivalTime: 03 Aug 2004 16:43:09.0057 (UTC) FILETIME=[F53B7F10:01C47978] X-WSS-ID: 6D111F2D2U81757552-10-01 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i73GhdpN030397 On Tuesday, August 03, 2004 11:39 AM, Christopher Faylor wrote > 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 >> >> >> $ 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 Consider it a "request for enhancement" without the requisite patch to be thoughtfully considered. -Jason PS - I apologize in advance for the legal disclaimer at the bottom of my email message. This is tacked on by our SMTP gateway and I have no control over it. -- ------------------------------------------------------------------------------ Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. ============================================================================== -- 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/