From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9350 invoked by alias); 8 Apr 2008 16:27:17 -0000 Received: (qmail 9334 invoked by uid 22791); 8 Apr 2008 16:27:15 -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 16:26:48 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 2D3596D4312; Tue, 8 Apr 2008 18:26:46 +0200 (CEST) Date: Tue, 08 Apr 2008 16:27:00 -0000 From: Corinna Vinschen To: cygwin-apps@cygwin.com Subject: Re: [HEADSUP] Let's start a Cygwin 1.7 release area Message-ID: <20080408162646.GC23852@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080404121534.GB3606@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/msg00087.txt.bz2 On Apr 4 14:15, Corinna Vinschen wrote: > On Apr 3 20:49, Christopher Faylor wrote: > > [responding to the thread which started it all] > > On Wed, Apr 02, 2008 at 02:35:51PM +0200, Corinna Vinschen wrote: > > >- We create a ftp://cygwin.com/pub/cygwin-1.7 dir. > > > > > >- Under that dir, we create the full release directory structure as it > > > exists in the parallel cygwin dir, except for the "cygwin" itself. > > > > So far so good. I'm just not sure we should really call it "cygwin-1.7". What would be a good name, which does not refer to the actual version number? "Cygwin" with uppercase C? I'm volunteering to create the directory layout... > > >- All files in the original release dir are hardlinked into their > > > matching spot in the cygwin-1.7 dir. > > > > I don't like hardlinking. It's too easy to have unintended side > > effects. I think I'd rather just symlink the directories in the new > > release area then rm the symlink and create a new directory when it's > > time to populate the directory with a 1.7 version. > > In theory I agree, but it lets more room for mistakes. It's very easy > to have a new package and just move the files to the directory, instead > of checking if the directory is a symlink or a real dir. If the dir > is a real dir from the start, you just dump the new package into the > dir and remove the oldest files and be done. > > Anyway, it's nothing I really get excited about. ...using the directory symlink approach. Could one of the setup.exe guys then create a matching setup.exe binary? Please? Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat