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: <435EDFA3.E5F66701@dessent.net>
Date: Tue, 25 Oct 2005 18:45:07 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cygwin-setup & rebaseall
References: <Pine DOT LNX DOT 4 DOT 64 DOT 0510241321510 DOT 5697 AT asterix> <435D743F DOT EDB6FBB9 AT dessent DOT net>  <Pine DOT LNX DOT 4 DOT 64 DOT 0510242312570 DOT 8868 AT asterix> <435DBB31 DOT 5C164C83 AT dessent DOT net> <Pine DOT LNX DOT 4 DOT 64 DOT 0510251133140 DOT 10334 AT asterix>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Satish Balay wrote:

> Doesn't setup have similar problem with updating 'packages' for
> running apps? I think it prompts for a reboot to complete. So I'm
> guessing the same approach can be used when it needs a rebase.

Yes, of course setup already has that logic.  That's what I was
referring to above about name.dll.new.  My point was that you can't just
have setup call the rebaseall script as a final step because the "in use
handling" of the two has to be in sync.  It has to be tightly
integrated.

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/