From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 86828 invoked by alias); 23 Nov 2017 20:54:11 -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 86810 invoked by uid 89); 23 Nov 2017 20:54:11 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,KB_WAM_FROM_NAME_SINGLEWORD,SPF_PASS autolearn=no version=3.3.2 spammy=our, Hx-spam-relays-external:ESMTPA, among X-HELO: vsmx009.vodafonemail.xion.oxcs.net Received: from vsmx009.vodafonemail.xion.oxcs.net (HELO vsmx009.vodafonemail.xion.oxcs.net) (153.92.174.87) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 23 Nov 2017 20:54:08 +0000 Received: from vsmx001.vodafonemail.xion.oxcs.net (unknown [192.168.75.191]) by mta-5-out.mta.xion.oxcs.net (Postfix) with ESMTP id 9DCBBC0454 for ; Thu, 23 Nov 2017 20:54:03 +0000 (UTC) Received: from Gertrud (unknown [87.185.219.5]) by mta-5-out.mta.xion.oxcs.net (Postfix) with ESMTPA id 748B430084A for ; Thu, 23 Nov 2017 20:54:01 +0000 (UTC) From: Achim Gratz To: cygwin-apps@cygwin.com Subject: Re: [PATCH setup 00/14] Use libsolv, solve all our problems... (WIP) References: <20170531105015.162228-1-jon.turney@dronecode.org.uk> <470d4572-4d63-81c2-7e26-6a642cce1e9f@cornell.edu> <2d099e44-fb17-4bf3-f72c-e6019a6259b3@dronecode.org.uk> <87d175f0qc.fsf@Rainer.invalid> <0d8c44ee-9665-041c-8c28-ee1bf42bd198@cornell.edu> <4126d612-8c49-1a1a-81fd-0105d563dc3d@dronecode.org.uk> Date: Thu, 23 Nov 2017 20:54:00 -0000 In-Reply-To: <4126d612-8c49-1a1a-81fd-0105d563dc3d@dronecode.org.uk> (Jon Turney's message of "Thu, 23 Nov 2017 18:10:21 +0000") Message-ID: <877eug1ztm.fsf@Rainer.invalid> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-VADE-STATUS: LEGIT X-SW-Source: 2017-11/txt/msg00104.txt.bz2 Jon Turney writes: >>> You can give each repo a priority and it will pick the package from the >>> one with the highest priority, even if another repo has a higher >>> version. >> >> Yes, that works. > > It seems that, when test versions are enabled, a test version is > preferred over a non-test version with a higher version > > I guess this is a consequence of: > >> void >> SolverPool::use_test_packages(bool use_test_packages) >> { >> // Give repos containing test packages higher priority than normal >> // if wanted, otherwise lower priority. >> SolvRepo::priority_t p = use_test_packages ? SolvRepo::priorityHigh : SolvRepo::priorityLow; > > I wonder if we just want to give test repos priorityNormal when they > are wanted? It really depends on what you are trying to achieve (and assuming you always work on all enabled repositories instead of specifically selecting one). 1) To chose the highest version available among a set of repositories (these need to be compatible in their versioning), then the priorities of all those repos need to be the same. 2) To prefer one repo over the other regardless of versioning (versioning need not be compatible), then raise the priority of the preferred repo. We currently can't use the difference between an update and distribution upgrade in setup since we would have to record which repo each package was originally installed from. If we had that, an update would keep the repository selection (even if another repo has a higher version) and a distribution upgrade would select the highest version, switching repositories as necessary. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds