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 To: cygwin AT cygwin DOT com From: Chuck Subject: Re: Installer option? Date: Tue, 30 Aug 2005 10:02:01 -0400 Lines: 36 Message-ID: References: <083020051356 DOT 19144 DOT 4314657D00054F7900004AC822069984990A050E040D0C079D0A AT comcast DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) In-Reply-To: <083020051356.19144.4314657D00054F7900004AC822069984990A050E040D0C079D0A@comcast.net> X-IsSubscribed: yes -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Eric Blake wrote: >>-----BEGIN PGP SIGNED MESSAGE----- >>Hash: SHA1 >> >>Is there a way to permanently tell the setup.exe program NOT to update >>my version of findutils? Recent versions do not traverse the registry if >>they encounter *'s in key names. The version I have (4.1.7-4) does. >>Everytime I want to update cygwin though I have to manually tell it to >>leave findutils alone. > > > This was fixed in a snapshot (and it was not so much the * character > in key names as a bug in open() on virtual directories). Otherwise, > you can wait for cygwin-1.5.19 when it is ready, and findutils-4.2.25 > when it is released upstream. In the meantime, sorry, there is no > way to force setup.exe to automatically not upgrade a file when a > newer version is available - it is a manual process every time you > run setup. :( > > -- > Eric Blake > > > Thanks. Do you know which snapshot has it? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) iEYEARECAAYFAkMUZtkACgkQzIf+rZpn0oTacwCgidCzSNZUrRdvmNuXu+hxWlrX BsQAn0hf4j1o5pDe3TCA1X1rshWFwuMN =wdnf -----END PGP SIGNATURE----- -- 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/