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 Message-ID: <029f01c58711$a479b2c0$0200000a@agamemnon> From: "Jon A. Lambert" To: References: Subject: Re: coreutils-5.3.0-8: lost *.exe Date: Tue, 12 Jul 2005 14:43:48 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Dave Korn wrote: >> From: fergus >>> Why did you do it? >> > > 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 have coreutils-5.2.1-5 sitting here in my releases directory but setup won't let me select it. How the heck do I get back to a working version of coreutils. -- 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/