X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Message-ID: <4D6CD103.7000303@gmx.de> Date: Tue, 01 Mar 2011 11:57:07 +0100 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Mnenhy/0.8.3 Thunderbird/3.1.7 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: setup.exe considerations (was: Doubtful about unison) References: <4D6BFD09 DOT 8020600 AT gmx DOT de> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 Am 01.03.2011 08:20, schrieb Andy Koppe: > On 28 February 2011 19:52, Matthias Andree wrote: >> 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). No it doesn't require such version dependencies. As a lightweight alternative, setup.exe might just recursively select all "requires" packages that a newly installed or upgraded package depends on "for update" (possibly from the same version branch, curr/test/prev), making sure not to implicitly downgrade. In this particular example, it would mark "alternatives" and "cygwin" for update as direct unison2.32 dependencies, and recursively also libintl8, libiconv2, base-cygwin, and libgcc1. On the other hand, Cygwin package maintainers do a pretty good job of not breaking existing setups, so "update everything" (to the "curr" version) is usually a safe bet.---I've been doing that for over four years and the only thing that hicc-upped regularly (and required rebasing or peflagsall) was git-svn. -- 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