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
Message-ID:	<43692452.70909@etr-usa.com>
Date:	Wed, 02 Nov 2005 13:40:50 -0700
From:	Warren Young <warren AT etr-usa DOT com>
User-Agent:	Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version:	1.0
To:	Cygwin-L <cygwin AT cygwin DOT com>
Subject:	Re: cygcheck improvements
References:	<SERRANOwAeRaNgEpTX5000000cf AT SERRANO DOT CAM DOT ARTIMI DOT COM>
In-Reply-To:	<SERRANOwAeRaNgEpTX5000000cf@SERRANO.CAM.ARTIMI.COM>
X-IsSubscribed:	yes

Dave Korn wrote:
>  if lots of
> packages register check-callbacks with cygcheck, we're going to end up
> (implicitly) making it dependent on a whole lot of other stuff being there and
> working.

You could create a new directory, say /etc/cygcheck[.d].  Any package 
that wants cygcheck to run a test for it could put a script in there, 
which cygcheck would run.  Then cygcheck doesn't need to have built-in 
knowledge of what scripts it should try to run.

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

- Raw text -