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: Sat, 29 Apr 2000 23:48:22 -0400 To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Added crude update ability to setup.exe Message-ID: <20000429234822.A870@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 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i I just made some changes to setup: 1) Store version information, gleaned from filenames in the registry. 2) Accept a "-u" option which will cause setup to run in "update mode", only downloading or installing newer versions of .tar.gz files. 3) Accept a list of packages to install on the command line. If setup.exe detects that an attempt is being made to install to a directory which seems to already have cygwin 1.1.0 in it, but there is no version information in the registry, it will ask the user if it should update the registry with default settings, appropriate for the previous installation. Anyway, what I'm aiming for is to be able to do something like this: setup -u cygwin And, for the most part, this works fine. One problem I have is that, right now, setup.exe uses HKLM to store the list of packages that have been installed. I guess I'll have to also use HKCU if the user can't write to HKLM. -- cgf AT cygnus DOT com Cygnus Solutions, a Red Hat company http://sourceware.cygnus.com/ http://www.redhat.com/