Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Authentication-Warning: frame.smarts.com: elbergr owned process doing -bs
Date: Tue, 16 Sep 2003 12:10:05 -0400 (EDT)
From: Rich Elberger <elbergr AT smarts DOT com>
X-X-Sender: elbergr AT frame
To: cygwin AT cygwin DOT com
Subject: Re: Upgrading Cygwin - postinstall difficulties?
In-Reply-To: <Pine.GSO.4.56.0309161149240.12411@slinky.cs.nyu.edu>
Message-ID: <Pine.SOL.4.50.0309161201120.28620-100000@frame>
References: <bk7ans$mum$1 AT sea DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 56 DOT 0309161149240 DOT 12411 AT slinky DOT cs DOT nyu DOT edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



> Well, you shouldn't run setup with Cygwin processes running in the first
> place.  I've been meaning to add an interactive dialog on failing to
> replace cygwin1.dll that would let you kill Cygwin processes and retry the
> replacement, but haven't got to it yet (and probably won't for quite a
> bit).
>

this is difficult to do and keep installation integrity.  better might be
finding processes/file handles open in the cygwin install area after
choosing the installation target area, and not allowing install to continue
until those processes shut down.  this is a classic installation issue,
and if you don't have cancel and (graceful) rollback, there will be a
loophole for failure.

-- rich


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