DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=WTnOOJe1brRLltgWRIcw69LdVitEgOeEzu1o/XBoRBxD4Ksli/5qI
	gJdVE3cpCF8CsuV3mP2fW7nZpJbQ5zI3eM4COOMtHr3ABq/nIPuGRrTtXu4IquGo
	jEnAO7ZzaeSlxFJuZv6nUaxCY8sKfEaJ4UI48d+T1zXZ3fEdvbKh1Q=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Mon, 4 Nov 2013 11:00:32 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: setup.ini dependency graph?
Message-ID: <20131104160032.GB5526@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
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> <5277AFEA DOT 9060404 AT cwilson DOT fastmail DOT fm>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5277AFEA.9060404@cwilson.fastmail.fm>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Mon, Nov 04, 2013 at 09:32:10AM -0500, Charles Wilson wrote:
>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...

Is this packagable?  It sounds pretty interesting.

Would it be crazy to generate this and make it available on the cygwin
web site?  Or would the dependency graph generation overload
sourceware.org?

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