From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 52705 invoked by alias); 6 Nov 2017 14:20:26 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 52675 invoked by uid 89); 6 Nov 2017 14:20:25 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=H*Ad:D*nl, highest, HCc:D*nl, Hx-spam-relays-external:ESMTPA X-HELO: out4-smtp.messagingengine.com Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 06 Nov 2017 14:20:24 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id C68F320AD6; Mon, 6 Nov 2017 09:20:21 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Mon, 06 Nov 2017 09:20:21 -0500 X-ME-Sender: Received: from [192.168.1.102] (host86-162-230-154.range86-162.btcentralplus.com [86.162.230.154]) by mail.messagingengine.com (Postfix) with ESMTPA id 58D0A2473E; Mon, 6 Nov 2017 09:20:21 -0500 (EST) From: Jon Turney Subject: Re: setup.ini has multiple "prev" entries ... Why? To: The Cygwin Mailing List Cc: Houder References: <20e5f0520f9831ecd59e509dc7f7d852@xs4all.nl> Message-ID: Date: Mon, 06 Nov 2017 14:20:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2017-11/txt/msg00122.txt.bz2 On 05/11/2017 17:32, Houder wrote: > On 2017-11-05 13:48, Houder wrote: >> After I had downloaded and exercised setup version 2.882, I noticed >> that setup.ini has multiple (2?) "prev" entries per package ... >> >> Why? Did I miss one of your announcements mentioning this change? > >     https://cygwin.com/ml/cygwin-apps/2017-10/msg00047.html > >> Because of the way setup works, the last [test] section is the version >> which >> is selected when 'test' is selected, so a specific ordering of the >> sections >>  would be required. ... >> [...] > So ... if I read the above correctly, the "prev" entries can be ordered > arbitrarily with respect to each other (within a package section) ????? > (and basically, the same question with respect to the "test" entries) Since [1], there's no way to install a prev version using setup, without explicitly selecting which version you want, so the ordering of those [prev] versions in setup.ini is relatively unimportant. [1] https://cygwin.com/ml/cygwin-apps/2011-07/msg00064.html However, you can tell setup to install "the test version", so we ensure that the highest version [test] section is last, to ensure it's the one that setup installs. > Meaning, one has to "interpret" the version id of each "prev" entry, > in order to be able to establish the _latest_ "prev" entry (i.e. the > version of the package before the current one) ? Yes. (Although due to historical mistakes with version numbers, that ordering might be wrong) -- 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