Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: <4154A0D5.C117AA80@dessent.net> Date: Fri, 24 Sep 2004 15:33:57 -0700 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Is setup.exe _supposed_ to delete the cygwin dll before attempting to run shell scripts? References: <20040924164839 DOT GJ674 AT trixie DOT casa DOT cgf DOT cx> <20040924170321 DOT GL12802 AT cygbert DOT vinschen DOT de> <011d01c4a266$19792470$78d96f83 AT robinson DOT cam DOT ac DOT uk> <41549A76 DOT 221A8526 AT dessent DOT net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Igor Pechtchanski wrote: > > You first get the depth-first order: D, C, B, A. > > > Properly speaking, the depth-first order will be B, D, C, A... > D'oh' > Unfortunately, this won't work when you have circular dependencies (e.g., > cygwin <-> fileutils). Oh, did I forget to say the graph must be a DAG before starting? :) Anyway, there are heuristics that could be used to find the best "feedback set" of edges for which removal would result in an acyclic graph. e.g. the one described at > I think Max's solution is probably the least complex short-term one (i.e., > run all preremove scripts in batch *before* removing any files, and hope > for the best). Yeah, probably true... I realize that people have probably already suggested these solutions involving graph theory in the past. And as you point out, a working patch is one thing, a bunch of conjecture is another. Brian -- 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/