From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16821 invoked by alias); 5 Dec 2008 17:00:03 -0000 Received: (qmail 16736 invoked by uid 22791); 5 Dec 2008 17:00:02 -0000 X-Spam-Check-By: sourceware.org Received: from out1.smtp.messagingengine.com (HELO out1.smtp.messagingengine.com) (66.111.4.25) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 05 Dec 2008 16:59:22 +0000 Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id DF7E91CDA8C for ; Fri, 5 Dec 2008 11:59:20 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 05 Dec 2008 11:59:20 -0500 Received: from [192.168.1.3] (user-0cej09l.cable.mindspring.com [24.233.129.53]) by mail.messagingengine.com (Postfix) with ESMTPSA id 83FDC290E5; Fri, 5 Dec 2008 11:59:20 -0500 (EST) Message-ID: <49395DE5.5090805@cwilson.fastmail.fm> Date: Fri, 05 Dec 2008 17:00:00 -0000 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.18) Gecko/20081105 Thunderbird/2.0.0.18 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: Mailing List: CygWin-Apps Subject: Re: Updated: 1.7.0-34 (...and a plea) References: <20081126124259.GA30831@calimero.vinschen.de> <20081205110733.GQ12905@calimero.vinschen.de> <2bf229d30812050505g17cb69c7y64a899a0a178a3cc@mail.gmail.com> In-Reply-To: <2bf229d30812050505g17cb69c7y64a899a0a178a3cc@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 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-12/txt/msg00032.txt.bz2 Chris Sutcliffe wrote: > 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? Corinna has been using a paired approach for openssh (e.g. simultaneous releases of -5 for cygwin-1.5 and -6 for cygwin-1.7, followed by -7/-8, etc.) For autotools, I "jumped" to the next multiple of 10 for the new -1.7 series of releases, reserving (e.g.) -3 to -9 for any future updates to the packages for -1.5. However, in those particular cases I do NOT expect any additional releases for -1.5 anyway, so -3 to -9 most likely will be forever "empty". But yeah, using the same release number for different -1.5 and -1.7 packages is just asking for trouble. -- Chuck