Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Message-ID: <39414D64.98D27B19@carlthompson.net>
Date: Fri, 09 Jun 2000 13:02:44 -0700
From: Carl Thompson <cet@carlthompson.net>
MIME-Version: 1.0
To: DJ Delorie <dj@delorie.com>
Cc: Cygwin List <cygwin@sourceware.cygnus.com>
Subject: Re: How does setup.exe handle duplicate files?
References: <3941086F.9AE1D33A@dothill.com> <200006091540.LAA00812@envy.delorie.com> <20000609114851.A22793@cygnus.com> <3941191E.F3A9432F@dothill.com> <200006091622.MAA04481@envy.delorie.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

DJ Delorie wrote:
> 
> > I don't see how this policy guarantees that the correct instance of
> > a duplicate file is always installed.
> 
> It doesn't.  There is no way to know which version is the correct
> version.  It's a problem that hasn't been solved yet.

Perhaps a quick and easy solution would be to rename the distribution
files so that they begin with the date.  That way you know that the most
recent file is installed, at least (provided the installer is sorting by
filename).  Or the installer could just sort by modification date (more
work).

Carl Thompson

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com