X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <26328317.post@talk.nabble.com> Date: Thu, 12 Nov 2009 15:33:11 -0800 (PST) From: aputerguy To: cygwin AT cygwin DOT com Subject: Re: Suggestion: Have setup.exe warn before upgrading 'cgywin' package itself In-Reply-To: <4AFC942B.2080708@bopp.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <26327934 DOT post AT talk DOT nabble DOT com> <4AFC942B DOT 2080708 AT bopp DOT net> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Jeremy Bopp writes: > BTW, this is not only a problem for the cygwin package. Literally any > package could have files which are in use at the time of replacement. > So any solution would need to take that into account. True but sometimes the perfect is the enemy of the good enough... The 'cygwin' package is just about guaranteed to be in use if you are doing anything cygwin related. If you did the warning for this and maybe also bash (assuming it locks files) then you would cover the key issues. -- View this message in context: http://old.nabble.com/Suggestion%3A-Have-setup.exe-warn-before-upgrading-%27cgywin%27-package-itself-tp26327934p26328317.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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