Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Date: Wed, 14 Nov 2001 16:55:40 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-apps AT cygwin DOT com
Subject: Re: RFP cygcheck
Message-ID: <20011114215540.GG9836@redhat.com>
Reply-To: cygwin-apps AT cygwin DOT com
Mail-Followup-To: cygwin-apps AT cygwin DOT com
References: <046b01c16d56$01e7d470$0200a8c0 AT lifelesswks>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <046b01c16d56$01e7d470$0200a8c0@lifelesswks>
User-Agent: Mutt/1.3.23.1i

On Thu, Nov 15, 2001 at 08:47:49AM +1100, Robert Collins wrote:
>Chris,
>    How do you feel about making cygcheck a separate package to
>cygwin1.dll.
>
>Why? becuase
>a) it's reporting on setup.exe issues as well as pure cygwin1.dll issues
>now.
>b) Updating setup may therefore require updating cygcheck, and I don't
>think that that should require updating 'cygwin'.
>c) With dependencies theres no concern about cygcheck not getting
>installed - just place it in base.

I've been thinking of breaking out all of the cygwin utilties into a
separate package, actually.  I have more changes that I want to make to
cygcheck and there are some strace changes coming.  It would be nice to
release those without having to regen the dll.

The problem is that it requires some magic in my snapshot/build project
and that requires some tuitness.

cgf