Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <42B19C95.5D0D4D6B@dessent.net> Date: Thu, 16 Jun 2005 08:36:53 -0700 From: Brian Dessent MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Cygwin bail-out: cygexpat-0.dll not found References: <507826902@web.de> <6.2.1.2.0.20050616100004.03d0bcf0@pop.prospeed.net> <20050616150856.GD10382@trixie.casa.cgf.cx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Report: -5.8/5.0 ---- Start SpamAssassin results * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * 0.1 AWL AWL: From: address is in the auto white-list ---- End SpamAssassin results X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Igor Pechtchanski wrote: > If it's ok to make cygcheck depend on wget, see > . > > FWIW, I'd suggest using the -p (--package-find) option for this in > cygcheck. I've noticed that the package-grep.cgi script can somwtimes take a while to complete, which is not surprising given that I've read that sourceware.org tends to be overworked. Adding a programmatic query to this would seem to just add more work for the poor server. Would it make sense to dump the "tar tjf" output of all the packages to a single static file on cygwin.com in a daily cronjob, and then just grab that file and search locally? Or is something similar already in place to facilitate the "cygwin.com/packages/foo/foo-1.2.3"-type pages? Brian -- 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/