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:	<cb51e2e041205175743f344e2@mail.gmail.com>
Date:	Sun, 5 Dec 2004 17:57:32 -0800
From:	Joshua Daniel Franklin <joshuadfranklin AT gmail DOT com>
Reply-To:	Joshua Daniel Franklin <joshuadfranklin AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: What depends on less and what man depends on.
In-Reply-To:	<n2m-g.couf1r.3vsgj61.1@buzzy-box.bavag>
Mime-Version:	1.0
References:	<n2m-g DOT couf1r DOT 3vsgj61 DOT 1 AT buzzy-box DOT bavag>
X-IsSubscribed:	yes

On Sun,  5 Dec 2004 08:13:34 +0100 (MET), Bas van Gompel wrote:
> Sometimes one wants to know what depends on a package or vice versa.
> 
> To find out, using the local setup.inis, I wrote following script.
> It uses make to recursively find and display all dependencies in
> either direction.

Buzz, 

These scripts you've made seem both cool and useful to me. It would
be even better if we had this functionality in some of the cygwin utils,
though, like cygcheck. Any interest in that?

I'm also thinking maybe setup.exe should store the latest known good
setup.ini as /etc/setup/setup.ini or something like that.

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