From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: Re: Questions about packaging Date: Fri, 18 Oct 2019 19:16:35 +0200 Message-ID: <87y2xix9cc.fsf@devup.no> References: <20191009095633.qlhnq2yvtp7dbrrf@rafflesia> <20191010024127.1da7c86d@scratchpost.org> <20191011074200.azkyt4mufjazbuj6@rafflesia> <20191012124116.6f842667@scratchpost.org> <20191014075154.glbillit5hu7p6vb@rafflesia> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:56789) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iLVrp-00079e-5v for guix-devel@gnu.org; Fri, 18 Oct 2019 13:16:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iLVrm-0005kH-T9 for guix-devel@gnu.org; Fri, 18 Oct 2019 13:16:44 -0400 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]:52445) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iLVrk-0005j7-I2 for guix-devel@gnu.org; Fri, 18 Oct 2019 13:16:41 -0400 In-Reply-To: <20191014075154.glbillit5hu7p6vb@rafflesia> 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: Tanguy Le Carrour , Danny Milosavljevic Cc: Guix --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello Tanguy, 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=C2=A0create 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. 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 :-) --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl2p83MACgkQoqBt8qM6 VPpZQQf/W9jKPw2gkRZzVdnMrXDMSi17k8DOUYzvHNI1Ycnd8VMcg0/cbUqQ88Wd 1ANb4YdgYrMNEOd0NwQqGmT/eAWrMYDYdzPbSLkieQq18/PKcZqaiIBKZ+aHbQVD m0JPK+MOw6Zsi9adSK+2wu/r0HMxbllM9x/WGDLYbXVUpozlCTzkw7hkKtPBsDEN EesduaIDkJa4AYJoDLeMhxgN3b/+kkQKf4pzZzkJWSSA+N2pd6g9cmK6cEOR/qfW A/mpNjbZRE8ajAy8zyV0InYkv/y6et/nPnn3rNRW3TP+OuVW7n1KS941pzrDAklL F4nTs8jhqTQmVVFJdNu0pcGizMOkwg== =Rdtw -----END PGP SIGNATURE----- --=-=-=--