From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21375 invoked by alias); 8 Apr 2008 21:54:28 -0000 Received: (qmail 21357 invoked by uid 22791); 8 Apr 2008 21:54:28 -0000 X-Spam-Check-By: sourceware.org Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Tue, 08 Apr 2008 21:54:10 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id EB28C6D4313; Tue, 8 Apr 2008 23:54:07 +0200 (CEST) Date: Tue, 08 Apr 2008 21:54:00 -0000 From: Corinna Vinschen To: cygwin-apps@cygwin.com Subject: Re: [HEADSUP] Let's start a Cygwin 1.7 release area Message-ID: <20080408215407.GC8083@calimero.vinschen.de> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <20080402123551.GB4468@calimero.vinschen.de> <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080408214608.GA8083@calimero.vinschen.de> User-Agent: Mutt/1.5.16 (2007-06-09) 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/msg00099.txt.bz2 On Apr 8 23:46, Corinna Vinschen wrote: > On Apr 8 14:16, Brian Dessent wrote: > > Okay, so, several years ago setup.exe HEAD was modified to look for > > "release" and "release_legacy" as the base dirname for packages > > depending on whether it was running on 9x/ME or NT/2k/etc. I understand > > Sorry, but I didn't remember that. Why didn't you just tell us? > > How do you differ the setup.ini files if you only have different release > subdirs? setup_legacy.ini? > > > that having Cygwin 1.7 playground is a different concept, but why should > > it be handled differently? Why not "release_1.7"? This is all > > temporary anyway IIUC, since it's just for testing packages built with > > 1.7, which will eventually all be moved over into just plain "release" > > anyway, right? If this is *not* temporary then how does it fit into the > > idea of having a legacy 9x/ME area? > > When I came up with that a couple of days ago, I thought it might be bad > to rename the current release area for 1.5 so that it keeps working as > is and downloading from the 1.7 release area requires to make the > conscience choice to use the 1.7 setup. If we can do this with a > release-1.7 plus a setup-1.7.ini file, than that's ok for me, too. And, apart from the actual names used, can we get a matching setup.exe perhaps this week? Or the next one? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat