X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: setup.exe considerations (was: Doubtful about unison) Date: Thu, 03 Mar 2011 08:45:35 -0500 Lines: 8 Message-ID: References: <4D6BFD09 DOT 8020600 AT gmx DOT de> <4D6CD103 DOT 7000303 AT gmx DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > I think it would be entirely reasonable to record the version you > built against as the minimum requirement, as you couldn't be expected > to test against older libraries as well. Wanting to use latest Unison > with an old Cygwin DLL is a case of having your cake and eating it, > it's just that it would be good if setup.exe was able to point that > out. But, in another bakery-related metaphor, this is pie-in-the-sky. I don't know, it seems half-baked to me :) -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple