Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Fri, 28 Apr 2000 12:13:02 -0400 To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: Time for a new DLL release Message-ID: <20000428121302.B1614@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com References: <20000428113914 DOT A1495 AT cygnus DOT com> <200004281608 DOT MAA05186 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i In-Reply-To: <200004281608.MAA05186@envy.delorie.com>; from dj@delorie.com on Fri, Apr 28, 2000 at 12:08:31PM -0400 On Fri, Apr 28, 2000 at 12:08:31PM -0400, DJ Delorie wrote: >>I would like to make a new release next week but I'm not 100% sure how >>to do this. I can put a new version of cygwin-whatever.tar.gz on the >>web site but we don't really want to have everyone download the entire >>distribution just to update cygwin. > >Accept the fact that setup doesn't support updates yet, and publish >instructions for a manual upgrade. It's not that hard to do if cygwin >is already installed, except that the dll needs to be moved into place >manually, which means untargz'ing in a temp directory, and using >explorer to move the files into place. I'm really leery of providing a manual upgrade procedure, given the incredible difficulties that people are having with the "manual" updating procedure with setup.exe. I guess it is possible to do this with a .bat file, though. cgf