X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Message-ID: <4EBB0593.2050105@cwilson.fastmail.fm> Date: Wed, 09 Nov 2011 17:58:27 -0500 From: Charles Wilson Reply-To: Charles Wilson User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: setup.exe, dependencies, and 'keep' mode References: <4EBB0211.1060508@cs.utoronto.ca> In-Reply-To: <4EBB0211.1060508@cs.utoronto.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 On 11/9/2011 5:43 PM, Ryan Johnson wrote: > There's a somewhat annoying behavior in setup.exe when installing > packages in 'keep' mode: all dependencies selected by things which would > have been installed in 'Curr' mode still try to download. Often I can It's a setup.hint "bug". While setup.exe does support per-version requires: statements, most setup.hints don't use that, and instead specify "global" requirements. So, bob uploads the new package "foo" which now requires libbar, and he simply modifies the (global) requirements to add libbar. When you try to "keep" the old foo, setup.exe still notices that the requirements now include libbar, and you don't have it installed, so... -- Chuck -- 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