From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23280 invoked by alias); 22 Jul 2008 09:32:47 -0000 Received: (qmail 23263 invoked by uid 22791); 22 Jul 2008 09:32:46 -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, 22 Jul 2008 09:32:20 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id CD3F06D4354; Tue, 22 Jul 2008 11:32:25 +0200 (CEST) Date: Tue, 22 Jul 2008 09:32:00 -0000 From: Corinna Vinschen To: cygwin-apps@cygwin.com Subject: Re: New Cygwin 1.7.0-18 in release-2 Message-ID: <20080722093225.GA15895@calimero.vinschen.de> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <20080717155516.GC5675@calimero.vinschen.de> <48851EE2.9030202@users.sourceforge.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48851EE2.9030202@users.sourceforge.net> 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-07/txt/msg00097.txt.bz2 On Jul 21 18:42, Yaakov (Cygwin Ports) wrote: > I've considered making the switch, as the new features in 1.7 (namely > IPv6 and wchar functions) would make porting *much* easier. It might > also provide the chance to finally close the gap between Ports and the > distro, and generally improve our packaging scheme at the same time. > > OTOH I don't have only myself to think about; with all my packages, I > doubt that I'll be able to support 1.5 any more after I switch. Not even pure security updates? > It would help if I could get some clarification on: > > *) When 1.7 goes gold (and I don't mean binutils!), is the recommended > upgrade path going to be in the same (Windows) tree, or to start fresh > in a new directory? When 1.7 goes gold, the idea is to install over an 1.5 install. Or not. It's the choice of the user. Installing over 1.5 is supported by the base-cygwin package, which is supposed to convert the registry mount points to /etc/fstab mount points. OTOH, a 1.7 install can coexist with a 1.5 install on the same machine. > *) Is gcc-4.3 in the near future for 1.7? Will gcc define > _GLIBCXX_USE_WCHAR_T? Will it provide shared libgcc, libstdc++, etc? That's one for Dave to answer. > *) Is there a roadmap of what needs to be done for 1.7? I know you > don't want to provide a date, but some focus and perspective would be > helpful. There's no roadmap. What's missing for a release is - A new setup.exe - The Cygwin utils are not quite up to speed - Documentation changes - Support by the package maintainers - Testing All of the above items could need a helping hand. If 1.7 isn't too buggy, I plan to release 1.7 still in 2008. When that actually happens doesn't depend on me. Cygwin 1.7 development has gone on for two years and it comes with a lot of changes. Not all of them allow a 100% smooth transition. Eventually this release depends on the support it gets from all of you. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat