X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4B47986F.2020609@t-online.de> Date: Fri, 08 Jan 2010 21:41:19 +0100 From: Christian Franke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Update problems References: <4B46A4C3.2000803@cygwin.com> In-Reply-To: <4B46A4C3.2000803@cygwin.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Larry Hall (Cygwin) wrote: > On 01/07/2010 09:39 PM, David Gast wrote: >> There are two problems with updating cygwin. >> >> 1. If you run setup.exe from bash, bash cannot be updated >> because the file is in use. > > Sure. This is the reason 'setup.exe' exists. It's a Windows > "feature" that keeps you from replacing a file that's in use. > 'setup.exe' was created to provide a native Windows program > to avoid the problem of something like 'setup.exe' needing to > update files that are in use by it. If it were possible to > replace files in use with the same ease as on Linux, say, > then 'setup.exe' would never be needed since things like > rpm, yum, and apt, to name a few, could be used directly > to install and update Cygwin. Cygwin 1.7 actually allows to replace an executable which is still in use: http://cygwin.com/ml/cygwin/2009-12/msg00423.html Christian -- 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