From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27928 invoked by alias); 13 Apr 2008 03:43:56 -0000 Received: (qmail 27915 invoked by uid 22791); 13 Apr 2008 03:43:55 -0000 X-Spam-Check-By: sourceware.org Received: from pool-72-74-94-32.bstnma.fios.verizon.net (HELO ednor.cgf.cx) (72.74.94.32) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 13 Apr 2008 03:43:38 +0000 Received: by ednor.cgf.cx (Postfix, from userid 201) id AF72B2B352; Sat, 12 Apr 2008 23:43:36 -0400 (EDT) Date: Sun, 13 Apr 2008 03:43:00 -0000 From: Christopher Faylor To: cygwin-apps@cygwin.com Subject: Re: [HEADSUP] Let's start a Cygwin 1.7 release area Message-ID: <20080413034336.GA11627@ednor.casa.cgf.cx> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <47FBE090.E3FAC05E@dessent.net> <20080408214608.GA8083@calimero.vinschen.de> <47FBFF63.3D2474FD@dessent.net> <20080409082646.GF23852@calimero.vinschen.de> <47FCB20D.DACDC9FA@dessent.net> <20080409121559.GA15549@calimero.vinschen.de> <47FCC01A.A9ABB7B9@dessent.net> <20080409143139.GA5920@ednor.casa.cgf.cx> <20080409162803.GL23852@calimero.vinschen.de> <20080411151333.GO23852@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080411151333.GO23852@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/msg00170.txt.bz2 On Fri, Apr 11, 2008 at 05:13:33PM +0200, Corinna Vinschen wrote: >On Apr 9 18:28, Corinna Vinschen wrote: >> On Apr 9 10:31, Christopher Faylor wrote: >> > On Wed, Apr 09, 2008 at 06:09:46AM -0700, Brian Dessent wrote: >> > >Corinna Vinschen wrote: >> > >>My favorite would be release-2. It has nothing to do with the DLL >> > > >> > >Sounds fine to me as well. >> > >> > It's ok. >> >> Oh, btw., can we really just use symlinks to the top-level dirs? >> It just occured to me that some package directories contain >> subdirectories for packages which are maintained by another >> maintainer. For instance the perl and python subdirs... > >I've now created a release-2 area. I used a somewhat intermediary >approach. The dirs are real dirs, the tar.bz2 files are symlinks >to the release area, the setup.hint and md5.sum files are copies. >The cygwin subdir only contains 1.7.0-1 packages. > >Chris, could you please set up another upset which creates the >corresponding setup-2.{bz2,ini} files? I have another way to do this using a union fs. Using a union fs means that we can have a cygwin-2 directory which mirrors the old cygwin directory, gaining the benefits of hardlinking, but also allowing removals in the new directory without affecting the old cygwin directory. I set up a release-2008 directory briefly under /sourceware/ftp/anonftp/pub/cygwin where I've removed all of the cygwin-1.5* files from the cygwin directory, left the existing setup.hint, and put cygwin-1.7* files there. The directory now contains the actual setup.hint from /sourceware/ftp/anonftp/pub/cygwin and the new files that are unique. The only downside to this is that the mirrors will apparently be copying all of the data twice. So, we could remove all of the obsolete files and older revisions from this new release directory to minimize the extra copying. I've always wanted to use a union fs and I think that, except for the hit on the mirrors, this is going to be the most problem free way of maintaining a separate build area. cgf