X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,TW_YG,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Andrew Schulman Subject: Re: setup.exe considerations (was: Doubtful about unison) Date: Tue, 01 Mar 2011 09:04:40 -0500 Lines: 13 Message-ID: References: <4D6BFD09.8020600@gmx.de> <4D6CD103.7000303@gmx.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@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com > >> Which is the problem: the unison command was compiled against a newer > >> cygwin1.dll than yours. > > > > To be fair, setup.exe ought to be able to resolve or warn about such > > version dependencies. Unfortunately the infrastructure for that isn't > > in place, as it would require version requirements to be expressed in > > packages' setup.hint files (rather than in their READMEs, as they are > > at the moment). It would also require packagers to know what the version requirements are. I can record what versions of things were installed when I built Unison - or better yet, get cygport to record that for me - but I don't really know whether it would break with an earlier or later version of cygwin, etc. -- 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