From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31247 invoked by alias); 21 Jul 2008 23:42:55 -0000 Received: (qmail 31234 invoked by uid 22791); 21 Jul 2008 23:42:54 -0000 X-Spam-Check-By: sourceware.org Received: from yw-out-1718.google.com (HELO yw-out-1718.google.com) (74.125.46.156) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 21 Jul 2008 23:42:31 +0000 Received: by yw-out-1718.google.com with SMTP id 9so581899ywk.38 for ; Mon, 21 Jul 2008 16:42:29 -0700 (PDT) Received: by 10.64.7.16 with SMTP id 16mr5660413qbg.44.1216683748528; Mon, 21 Jul 2008 16:42:28 -0700 (PDT) Received: from ?192.168.0.101? ( [24.76.249.6]) by mx.google.com with ESMTPS id 25sm7676637qbw.1.2008.07.21.16.42.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 21 Jul 2008 16:42:28 -0700 (PDT) Message-ID: <48851EE2.9030202@users.sourceforge.net> Date: Mon, 21 Jul 2008 23:42:00 -0000 From: "Yaakov (Cygwin Ports)" User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: cygwin-apps@cygwin.com Subject: Re: New Cygwin 1.7.0-18 in release-2 References: <20080717155516.GC5675@calimero.vinschen.de> In-Reply-To: <20080717155516.GC5675@calimero.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/msg00095.txt.bz2 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Corinna Vinschen wrote: | again I would like to encourage the Cygwin maintainers, to try the new | Cygwin 1.7.0 release and to look for problems in their packages which | might be a result of the fairly massive changes in Cygwin 1.7. I | attached a list of the changes below. The latest changes are: 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. 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? *) 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? *) 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. Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiFHuIACgkQpiWmPGlmQSOYMACfUJJNNcUFVxtD+PYv4SSpaVIh kJUAnRF44vDumN4ScJX/sjcgly9lO/9M =xoP5 -----END PGP SIGNATURE-----