delorie.com/archives/browse.cgi | search |
On Sat, Mar 24, 2001 at 03:42:08PM +1100, Robert Collins wrote: >----- Original Message ----- >From: "Christopher Faylor" <cgf AT redhat DOT com> >To: <cygwin-developers AT cygwin DOT com> >Sent: Saturday, March 24, 2001 2:25 PM >Subject: Re: setup revisit > > >> On Sat, Mar 24, 2001 at 02:19:32PM +1100, Robert Collins wrote: >> > >> >Oh. That wouldn't have affected what I was suggesting (the current >> >cygwin1.dll would be used unless an update was present - in which >case >> >it comes back to the current setup's behaviour.). >> >> And if the current cygwin1.dll is B20? Do you want to rely on that? >> Or if it is a buggy snapshot? > >"unless an update was present". Then it upgrades cygwin1.dll first - and >if it can't either gives the current cygwin1.dll upgrade failure "can't >open", or [insert desired message/action]. So you'd have a side channel, special case method for updating the cygwin DLL which didn't rely on the cygwin DLL? That sounds messy to me. cgf
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |