From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 71898 invoked by alias); 6 Dec 2016 14:41:58 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 69214 invoked by uid 89); 6 Dec 2016 14:41:57 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_40,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=cygwinapps, jun, Jun, eligible X-HELO: out2-smtp.messagingengine.com Received: from out2-smtp.messagingengine.com (HELO out2-smtp.messagingengine.com) (66.111.4.26) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 06 Dec 2016 14:41:46 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 34C49206A7 for ; Tue, 6 Dec 2016 09:41:44 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Tue, 06 Dec 2016 09:41:44 -0500 X-ME-Sender: Received: from [192.168.1.102] (host86-179-112-226.range86-179.btcentralplus.com [86.179.112.226]) by mail.messagingengine.com (Postfix) with ESMTPA id CF7B224789 for ; Tue, 6 Dec 2016 09:41:43 -0500 (EST) Subject: Re: [PATCH setup] Allow setup to parse more than 3 versions from the setup.ini file To: cygwin-apps@cygwin.com References: <1433349024-9776-1-git-send-email-jon.turney@dronecode.org.uk> <20150608134318.GO3416@calimero.vinschen.de> <05b7266e-6a83-b860-9079-f8fd8c310175@dronecode.org.uk> From: Jon Turney Message-ID: <4f1cf795-ad84-7ab6-5976-82f8c33812bc@dronecode.org.uk> Date: Tue, 06 Dec 2016 14:41:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <05b7266e-6a83-b860-9079-f8fd8c310175@dronecode.org.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2016-12/txt/msg00000.txt.bz2 On 31/08/2016 11:48, Jon Turney wrote: > On 08/06/2015 14:43, Corinna Vinschen wrote: >> On Jun 3 17:30, Jon TURNEY wrote: >>> Reminded by a recent request as to how to install >>> xorg-server-1.17.1-2, which >>> has disappeared beyond setup's ken (in order to determine if there was a >>> regression in the curent version), this is a re-send of a patch I >>> originally >>> submitted back in 2011 [1], which received an ambiguous response then. >>> >>> [1] https://cygwin.com/ml/cygwin-apps/2011-04/msg00053.html >>> >>> This recognizes any "[foo]" line as introducing the information for >>> another >>> version, which doesn't have one of the trust levels [curr], [prev] or >>> [test], >>> and so isn't automatically selected when setup is told to install all >>> packages >>> at that trust level (by default, [curr]). >>> >>> Setup already does all the neccessary sorting in version order etc. >>> to use these >>> additional versions. >>> >>> Since the value of carries no meaning, it might make sense to >>> update the >>> setup.ini specification to mandate the use of specific strings like >>> "[also]" or >>> "[other]", or perhaps "[prev-1]", "[prev-2]", etc. >>> >>> I have written a corresponding patch to genini. >>> >>> I'm not sure what expiry policy is currently used by upset for old >>> packages, but >>> presumably that would need to be made more sophisticated, along with >>> the changes >>> needed to generate setup.ini entries for other versions. >> >> Upset does not handle expiry of packages at all. Versions are mentioned >> in setup.hint as test, curr, prev, or exp (yes, really) and those are >> handled, everything else throws an error message. Package versions not >> mentioned in setup.hint are simply ignored. > > Yes, upset doesn't (didn't) explicitly handle expiry, but the fact that > a package version is not mentioned in setup.ini causes it to be removed > by stalepkgs, when that is next run. > > After the corresponding change to setup.ini generation, it will list all > versions, so none would ever be eligible for expiry under that policy. > > Anyhow, improving that is close to the top of my hit-list for calm. calm now handles package expiry as of [1], so, pinging this. There also exists a corresponding calm patch [2], to generate setup.ini listing more than 3 versions (This should not be deployed until some time after a setup with the above patch has been released) [1] https://cygwin.com/ml/cygwin-apps/2016-09/msg00021.html [2] https://github.com/jon-turney/calm/commit/cf5497063b146cc7442437b5047e318d9a074769