X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:cc:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=Cv3MgNQf1NB8TqxY raljbJ9tS1CPAfZZ6uOA47R/yClvu1ioO5Ml0b98ldav1qzwmHuqChCwQRDAh+O9 oi0UnF5D/kCASGz3vejydO0Uu3MXhszbFRkQGZ7cAXEGHs1EDzMsO2bDljglq8EU sxn4iFKWwUxI29DpGlZyU60xOWs= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:cc:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=a2sw8UXhPFCARQYhSlsCdn qnijg=; b=IFmd6kFDs/S47eevsArLjhFGsj1MeuF0y0Ikhk05AHkvqdpec3DwFJ Sy/PGTl7rztJoHxKBHgezrYPgPP+MFOZ5uTcFvI2bGIn52+zrgm9yXxuuMKUm7bv /HVpSYS25mow7YD9AAlyxn+Y2Hm5J84VFeqtMPboM72/nuhlCvnTU= 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=Hx-spam-relays-external:ESMTPA X-HELO: out4-smtp.messagingengine.com X-ME-Sender: Subject: Re: setup.ini has multiple "prev" entries ... Why? To: Houder References: <20e5f0520f9831ecd59e509dc7f7d852 AT xs4all DOT nl> Cc: The Cygwin Mailing List From: Jon Turney Message-ID: Date: Mon, 6 Nov 2017 17:37:42 +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: 7bit On 06/11/2017 16:34, Houder wrote: > On 2017-11-06 15:20, Jon Turney wrote: > [snip] > >> I try to keep [1] accurate and up-to-date, but the 'specification' is >> really "what setup accepts" :( >> >> Currently, the ordering requirements are: >> >> 1) The version to be installed when test versions are selected (the >> highest test, unless one is explicitly specified in override.hint) is >> the last [test] section >> >> 2) [curr] is first >> >> But since both these things are to work around historical setup >> limitations, I don't think they merit mention in [1], and might not be >> the case in a future when we no longer care about setup versions old >> enough to need them. >> >> [1] https://sourceware.org/cygwin-apps/setup.ini.html > > But if the order of the versions is to be based _solely_ on "version", > which until now was merely an identifier (like "aap", "noot", "mies"), In fact, setup makes some decisions based on label, and some based on version ordering, which part of the current mess... > that is without any order, then both semantics and syntax of "version" > must be rigidly defined in [1] ... > > ... if you want it to be a specification for setup.ini. I'm not sure it belongs there, but the ordering is defined (see [2]) [2] https://cygwin.com/packaging-package-files.html#naming -- 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