From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4737 invoked by alias); 5 Dec 2008 13:06:12 -0000 Received: (qmail 4724 invoked by uid 22791); 5 Dec 2008 13:06:12 -0000 X-Spam-Check-By: sourceware.org Received: from rv-out-0708.google.com (HELO rv-out-0708.google.com) (209.85.198.251) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 05 Dec 2008 13:05:24 +0000 Received: by rv-out-0708.google.com with SMTP id b17so4518046rvf.38 for ; Fri, 05 Dec 2008 05:05:22 -0800 (PST) Received: by 10.141.53.18 with SMTP id f18mr7517941rvk.188.1228482322387; Fri, 05 Dec 2008 05:05:22 -0800 (PST) Received: by 10.141.89.19 with HTTP; Fri, 5 Dec 2008 05:05:22 -0800 (PST) Message-ID: <2bf229d30812050505g17cb69c7y64a899a0a178a3cc@mail.gmail.com> Date: Fri, 05 Dec 2008 13:06:00 -0000 From: "Chris Sutcliffe" To: cygwin-apps@cygwin.com, cygwin-developers@cygwin.com Subject: Re: Updated: 1.7.0-34 (...and a plea) In-Reply-To: <20081205110733.GQ12905@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081126124259.GA30831@calimero.vinschen.de> <20081205110733.GQ12905@calimero.vinschen.de> X-IsSubscribed: yes 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-12/txt/msg00023.txt.bz2 > On the not so bright side, I'm a bit disappointed that only few > maintainers are actually rebuilding their applications for 1.7. All > applications will probably profit at least from the now long pathnames > up to 32K. And many network related applications will profit from IPv6 > support and the new getaddrinfo family of functions. For the packages I maintain (w32api, mingw-runtime, hexedit, astyle) I didn't think there would be much of an impact between 1.5 and 1.7. If there is some benefit, please let me know and I will build 1.7 versions of these packages. Is there a naming convention or something I should use, since I assume using the same name / version as the 1.5 binaries may cause a problem? Chris -- Chris Sutcliffe http://emergedesktop.org