From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9534 invoked by alias); 11 Apr 2010 19:13:12 -0000 Received: (qmail 9521 invoked by uid 22791); 11 Apr 2010 19:13:12 -0000 X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SARE_MSGID_LONG45,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Received: from mail-iw0-f201.google.com (HELO mail-iw0-f201.google.com) (209.85.223.201) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 11 Apr 2010 19:13:07 +0000 Received: by iwn39 with SMTP id 39so4201566iwn.2 for ; Sun, 11 Apr 2010 12:13:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.150.12 with HTTP; Sun, 11 Apr 2010 12:13:05 -0700 (PDT) In-Reply-To: <87pr266v6x.fsf@gmail.com> References: <87pr266v6x.fsf@gmail.com> Date: Sun, 11 Apr 2010 19:13:00 -0000 Received: by 10.231.167.65 with SMTP id p1mr1430030iby.20.1271013185450; Sun, 11 Apr 2010 12:13:05 -0700 (PDT) Message-ID: Subject: Re: Setup, update thyself From: Rance Hall To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2010-04/txt/msg00531.txt.bz2 On Sun, Apr 11, 2010 at 7:16 AM, Paul Bibbings wr= ote: > Given how the process of updating packages using setup.exe can be > handled quite automatically - updates are announced, mirrors catch-up, > and the recent updates can be picked up with a run through setup that > requires no interaction at all except to cycle through the `next's - I'm > wondering how it might be that updating of setup.exe is not itself > managed by this same process. =A0I am certainly notified if setup.exe is > out of date, which then triggers the manual process of shutting it down, > going to the website, grabbing the latest version and starting again. > Could not this process be integrated into setup itself as "just another > package install" in effect? Notification that setup.exe is out of date - > general package selection is disabled - `Next' etc. downloads setup.exe > as a `package' - automatic restart - continue from here...? > Excellent idea, but difficult to manage since windows has difficulty replacing files that are in use. Windows command shell scripting is well, lacking. The standard way to do this would be to write a script that wgets (or other windows alternative) the setup.exe on the web into a staging area. Run setup -v or some other appropriate switch to get a version number on both the cygwin setup and the new one. If needed replace them. and then run your standard update using the new setup. It works well, but I may be changing it to a fatal error when setup.exe changes. The switch between 1.5 and 1.7 could not have been handled automatically without some study as to pitfalls, etc. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple