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: Thu, 16 Jun 2005 12:18:23 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin bail-out: cygexpat-0.dll not found
Message-ID: <20050616161823.GM10382@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <507826902 AT web DOT de> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050616100004 DOT 03d0bcf0 AT pop DOT prospeed DOT net> <20050616150856 DOT GD10382 AT trixie DOT casa DOT cgf DOT cx> <Pine DOT GSO DOT 4 DOT 61 DOT 0506161120470 DOT 4978 AT slinky DOT cs DOT nyu DOT edu> <42B19C95 DOT 5D0D4D6B AT dessent DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <42B19C95.5D0D4D6B@dessent.net>
User-Agent: Mutt/1.5.8i

On Thu, Jun 16, 2005 at 08:36:53AM -0700, Brian Dessent wrote:
>Igor Pechtchanski wrote:
>>If it's ok to make cygcheck depend on wget, see
>><http://cygwin.com/ml/cygwin/2005-06/msg00726.html>.
>>
>>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.

sourceware.org is somewhat less overworked these days after some recent
performance tweaks.  I'm doing more spam blocking at the SMTP level,
we've remounted some of the disks using EXT2 rather than EXT3, and I'm
throttling some problematic http connections -- all seem to account for
some improvement.  There is also a new super machine on order so this
will not be an issue by the end of the year.

>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?

That would be static, out-of-date data, just ripe for "I just did a
'cygcheck --whatprovides cygintl-2.dll' and the package don't exist!!!!"
type of messages.

OTOH, Red Hat gets away with this by providing a massive rpm static
database for --redhatprovides queries.  Of course Red Hat also provides
monolithic releases, unlike Cygwin.

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/