From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22249 invoked by alias); 23 Nov 2012 17:16:30 -0000 Received: (qmail 22100 invoked by uid 22791); 23 Nov 2012 17:16:25 -0000 X-SWARE-Spam-Status: No, hits=-4.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_BJ,TW_GC X-Spam-Check-By: sourceware.org Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com) (209.85.212.179) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 23 Nov 2012 17:16:20 +0000 Received: by mail-wi0-f179.google.com with SMTP id hj6so1391070wib.2 for ; Fri, 23 Nov 2012 09:16:18 -0800 (PST) Received: by 10.180.102.161 with SMTP id fp1mr7360890wib.9.1353690978817; Fri, 23 Nov 2012 09:16:18 -0800 (PST) Received: from [192.168.2.99] (cpc3-cmbg8-0-0-cust629.5-4.cable.virginmedia.com. [82.6.102.118]) by mx.google.com with ESMTPS id ec3sm9352982wib.10.2012.11.23.09.16.16 (version=SSLv3 cipher=OTHER); Fri, 23 Nov 2012 09:16:17 -0800 (PST) Message-ID: <50AFAFB0.7040006@gmail.com> Date: Fri, 23 Nov 2012 17:16:00 -0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin-apps Subject: Changing dependent library version numbers vs. test packages vs. requires: lines. 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: 2012-11/txt/msg00064.txt.bz2 Hi all, I've got a gcc-4.7.2 package almost ready to upload, but there's one issue I'm not sure what's best to do about. Several of the runtime libs have changed version numbers, i.e. libgnat4.5->libgnat4.7, libgcj11->libgcj13, libobjc2->libobjc4. I'd like to release a test: version of the new compiler, but I don't know what's best to do for the requires: lines in the setup hint files. If I add the new library versions, those dependencies will also be pulled in by people installing the curr: version of the compiler, but the new libraries won't exist in curr: versions. If I don't, people installing the test: version will have to ensure they manually select the new runtime libraries, which might be the least worst option. Is there any better way to handle this situation? cheers, DaveK