Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Thu, 18 May 2000 12:21:01 -0400 To: cygwin@sourceware.cygnus.com Subject: Re: Setup.exe update problem Message-ID: <20000518122101.B10769@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cgf@cygnus.com, cygwin@sourceware.cygnus.com References: <200005161823.OAA27811@allman.localnet.com> <39240BE3.5F2E6CC0@bigfoot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i In-Reply-To: <39240BE3.5F2E6CC0@bigfoot.com>; from dumser@bigfoot.com on Thu, May 18, 2000 at 10:27:31AM -0500 On Thu, May 18, 2000 at 10:27:31AM -0500, James Dumser wrote: >Setup appears to use the current time as the "timestamp" used to track >packages. So when I downloaded 2000*, its install time was the current >time. When 1.1.1 later was propagated to the mirror, it retained the >timestamp from sourceware, which was earlier than 2000*'s install time >so setup didn't see 1.1.1 as an update. > >Maybe install time is a good thing to track; but for updates, what is >really needed is the file's timestamp. 1) There should only be one cygwin file in latest and it should be 'cygwin-1.1.1.tar.gz'. If setup installed two files, that probably means that you weren't installing from an empty directory. 2) Setup does not use install time to track updates. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com