From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tanguy Le Carrour Subject: Re: Questions about packaging Date: Mon, 21 Oct 2019 11:23:20 +0200 Message-ID: <20191021092320.rirojs26u6vshivn@rafflesia> References: <20191009095633.qlhnq2yvtp7dbrrf@rafflesia> <20191010024127.1da7c86d@scratchpost.org> <20191011074200.azkyt4mufjazbuj6@rafflesia> <20191012124116.6f842667@scratchpost.org> <20191014075154.glbillit5hu7p6vb@rafflesia> <87y2xix9cc.fsf@devup.no> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:34853) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iMTuO-0003NC-CR for guix-devel@gnu.org; Mon, 21 Oct 2019 05:23:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iMTuN-0002sM-9u for guix-devel@gnu.org; Mon, 21 Oct 2019 05:23:24 -0400 Received: from relay6-d.mail.gandi.net ([217.70.183.198]:45729) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iMTuN-0002rn-30 for guix-devel@gnu.org; Mon, 21 Oct 2019 05:23:23 -0400 Content-Disposition: inline In-Reply-To: <87y2xix9cc.fsf@devup.no> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Marius Bakke Cc: Guix Hi Marius, Le 10/18, Marius Bakke a écrit : > Tanguy Le Carrour writes: > > In Guix, we have Pytest 4.4.2, but the latest release is 5.2.1. > > In that case, would it make sense to define a new "versionned" public > > variable for python-pytest? Would I create python-pytest5? Or would I > > rename python-pytest to python-pytest4 and add python-pytest for Pytest > > 5? In this later case, would I have to "fix" all the packages that were > > using python-pytest?! > > Pytest has 4457 dependent packages and can thus only be changed on the > 'core-updates' branch. So the recommended way is indeed to define a new > public 'python-pytest-5' variable, and add that as an input for the > packages that require 5.x. OK… sounds like something I can do! > On the next 'core-updates' cycle, Pytest 5 will then become the default, > and we will have to fix all packages that does not work with that > version :-) I guess those broken packages will show up as "red" in Cuirass!? Would they have to be fixed, or just told to use python-pytest-4? Is there a way to build those packages on my machine? What a script to find and build all the packages dependent on pytest would look like? I mean, using LISP/Scheme/Guile, as I think I could come up with a "manual" solution with `guix graph --type=reverse-package`. Regards, -- Tanguy