From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26715 invoked by alias); 9 Apr 2008 11:34:45 -0000 Received: (qmail 26704 invoked by uid 22791); 9 Apr 2008 11:34:45 -0000 X-Spam-Check-By: sourceware.org Received: from dessent.net (HELO dessent.net) (69.60.119.225) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 09 Apr 2008 11:34:27 +0000 Received: from localhost ([127.0.0.1] helo=dessent.net) by dessent.net with esmtp (Exim 4.50) id 1JjYZN-0004Gp-W6 for cygwin-apps@cygwin.com; Wed, 09 Apr 2008 11:34:26 +0000 Message-ID: <47FCB20D.DACDC9FA@dessent.net> Date: Wed, 09 Apr 2008 11:34:00 -0000 From: Brian Dessent Reply-To: cygwin-apps@cygwin.com X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin-apps@cygwin.com Subject: Re: [HEADSUP] Let's start a Cygwin 1.7 release area References: <20080404004949.GA10978@ednor.casa.cgf.cx> <20080404121534.GB3606@calimero.vinschen.de> <20080408162646.GC23852@calimero.vinschen.de> <20080408172646.GA2089@ednor.casa.cgf.cx> <20080408174013.GD23852@calimero.vinschen.de> <20080408184148.GA2448@ednor.casa.cgf.cx> <20080408210726.GA7867@calimero.vinschen.de> <47FBE090.E3FAC05E@dessent.net> <20080408214608.GA8083@calimero.vinschen.de> <47FBFF63.3D2474FD@dessent.net> <20080409082646.GF23852@calimero.vinschen.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-04/txt/msg00112.txt.bz2 Corinna Vinschen wrote: > Yes. I'm just wondering if we could do without the final rename of the > directories. The Cygwin release area isn't that small, > 4 Gigs. A > simple top-level directory rename will force all mirrors world-wide to > copy the whole area. Twice, because we will have two release areas. > > If that's a minor concern, we do as above. Otherwise, I'd suggest to > create a "release-2" area and to update just setup.exe accordingly. We can still rename the .ini files without renaming the directory trees, it's all just a matter of how the upset cron job runs. I'm not sure if that really buys any clarity, but what it does do is allow us to "swap in" the entire staging area atomically once 1.7 is released. Otherwise, only users who updated their setup.exe would ever see the 1.7 release. I can almost see the email messages now: "Is Cygwin dead? I haven't seen a new release of the DLL or any updated packages in the last months?!?!" Brian