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 From: "Dave Korn" To: Subject: RE: coreutils-5.3.0-8: lost *.exe Date: Tue, 12 Jul 2005 18:20:38 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <1121187533.5551.4.camel@localhost.localdomain> Message-ID: ----Original Message---- >From: fergus >Sent: 12 July 2005 17:59 >> Why did you do it? > > Slightly bemused, I'll treat the question seriously. > Using setup.exe, the upgrade was offered, presumably through setup.ini. > There it is (timestamp 1121177436): coreutils 5.3.0-8, replacing 5.3.0-7. > > Fergus Well, yes; it's a serious question, although I left the point of it somewhat implicit, for dramatic effect! :) That point being, "If it aint broke, don't fix it". You asked what was the best thing you could have done or could do in future to avoid this kind of problem; my answer is this: If you aren't under some pressing and *urgent* need to upgrade a package because you vitally need a bugfix or new feature, DON'T! You're on a hiding to nothing if you do; nothing to gain, because you've already got what you want from the package; lots to lose, because sometimes upgrades are buggy. Leave the new releases alone for a few days after they've been announced and see if problems crop up! The only benefit is a warm fuzzy feeling of having the very latest version. That's not worth risking the costs! I call this "DaveK's law of installation stability" :) cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/