On Tue, Aug 03, 2004 at 12:38:41PM -0400, 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 >><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.
Btw, /etc/inetd.conf doesn't actually come from xinetd and the string /etc/inetd.conf doesn't actually occur in xinetd.lst.gz so this is a very good example of why it is dangerous to roll your own tools if you don't know what is going on. From the above, a novice user would assume that xinetd contained /etc/inetd.conf. /etc/inetd.conf is a generated file so it is not listed in the package lists of any package. -- 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/