X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=S2LJfkHkJV2xM5d3eGNEDLWlOwmkulZ2cXri9BRV7El
	JyGF9qWPtopk0MtcL1or6NdeXdNJEGk/KwxxbT/+e6X0yWBewD/KKfzSwqMwP1ET
	5fyzoGTiM/XfdXuTXKTJroahzQ0YUZ+64krRp49WEwciGvnCjHz08e0JYsfLTnsQ
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=6V7L55GUrpZXHy8bv8p7VHx2jJg=; b=hM0cu5/EQCdV2DW2H
	Yxr64wQZsbBpPBWVukvGSL8j+dSR5eHzb13ksCUxcMsZX+YMvzwcV8i0ma39wwwb
	OCeNN+y1JgaMvhoSHvhzWyeoDvKbRGb2ClJVi7LsnLOqLTVOOghdT88UFB9AJxOw
	3svmRv5/QOrondRJmwaXgOQZvw=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no version=3.3.2
X-HELO: out4-smtp.messagingengine.com
Message-ID: <5277AFEA.9060404@cwilson.fastmail.fm>
Date: Mon, 04 Nov 2013 09:32:10 -0500
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
Subject: Re: setup.ini dependency graph?
References: <526A986D DOT 9040202 AT cwilson DOT fastmail DOT fm> <526B8DF9 DOT 5000004 AT tiscali DOT co DOT uk> <5271000D DOT 7000604 AT cwilson DOT fastmail DOT fm> <52710EC5 DOT 2020403 AT cs DOT utoronto DOT ca>
In-Reply-To: <52710EC5.2020403@cs.utoronto.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 10/30/2013 9:51 AM, Ryan Johnson wrote:
> On 30/10/2013 8:48 AM, Charles Wilson wrote:
>> Yeah; even for my stripped-down version, I need to pre-process the
>> setup.ini and remove all mentions of cygwin, libstdc++6, libgcc1, etc.
>> The ncurses DLLs are also a huge nexus.  (It's probably easier to
>> exclude those nodes by mucking with the perl, but...)
> Quick question: do you have 1+ known-big-unwanted packages and need to
> know who's pulling them in, or are you hoping to take some cut of the
> graph that gets as many desirable packages as possible given the space
> constraints? The graph-building script here is good for the latter, but
> I had the impression you were doing the former; if so, my script might
> get you to an answer faster by avoiding information overload.

A combination of the two, actually.  I've used both David's script and 
yours in concert.  In addition, I've modified David's script to color 
the nodes based on origination, and to exclude or collapse 'Base' and/or 
'required-by-Base' packages.

I've got a few cleanups, and then I'll share the result.  It's already 
helped me generate a few re-packaging requests I plan to post over on 
cygwin-apps...

--
Chuck



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple