From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 98250158042 for ; Sun, 20 Oct 2024 10:46:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BCAD4E0821; Sun, 20 Oct 2024 10:46:33 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 8266CE07FA for ; Sun, 20 Oct 2024 10:46:33 +0000 (UTC) Message-ID: <3413fe34b8a530c98685a2b6bbf00eaee6e3c02f.camel@gentoo.org> Subject: Re: [gentoo-dev] Slotting PyPy From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= To: gentoo-dev@lists.gentoo.org Date: Sun, 20 Oct 2024 12:46:28 +0200 In-Reply-To: References: Organization: Gentoo Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-fMvSnfjmTrA69X1R0RoU" User-Agent: Evolution 3.52.4 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 X-Archives-Salt: ba96aeda-a58e-4566-b0c5-423285113969 X-Archives-Hash: e9101edf6496c8f8f449250be1447ad4 --=-fMvSnfjmTrA69X1R0RoU Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, 2024-10-17 at 14:12 +0200, Micha=C5=82 G=C3=B3rny wrote: > The ebuilds could now depend e.g. on: >=20 > >=3Ddev-lang/pypy-3.10:=3D >=20 > This would ensure that only slots newer than 3.10 are acceptable, > and that packages are rebuilt (as they are right now) once we introduce > 3.11 slot. Then, after the transitional period we'd update it to: >=20 > >=3Ddev-lang/pypy-3.11:=3D >=20 > and so on. >=20 Ok, I've missed something significant here. Along all the reshuffling, dev-python/pypy3 is not really a virtual package but supplies /usr/bin/pypy3 (vs. pypy3.x supplied by dev- python/pypy3_x). Switching to one-package model would require us to install "pypy3" as part of the baseline package, and that is going to make transitions less friendly. In other words, with the old approach, you could have pypy3.10 and pypy3.11 installed simultaneously, and switch to 3.11 via upgrading dev-python/pypy3 metapackage. With the new approach, we won't be able to have fully coexisting pypy3.10 and pypy3.11 packages without them conflicting over /usr/bin/pypy3. During the transition period, we'd have to have something like USE=3Dsymlink to clearly distinguish the PyPy version that satisfies PYTHON_TARGETS from the other one. Not saying it's a fatal flaw but certainly makes things less nice. I don't see any "obviously nice" solutions, other than having a separate metapackage for the purpose of keeping /usr/bin/pypy3. But then, merging dev-python/pypy3_x becomes a meaningless implementation detail. --=20 Best regards, Micha=C5=82 G=C3=B3rny --=-fMvSnfjmTrA69X1R0RoU Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iQFGBAABCgAwFiEEx2qEUJQJjSjMiybFY5ra4jKeJA4FAmcU34QSHG1nb3JueUBn ZW50b28ub3JnAAoJEGOa2uIyniQOxmEH+wVzJGP8PBe7jlM1942ox+f21OtfhCB6 QYiK0Eg9yq0ozyHdN660TU1HNzZS3G/C89hIka739qasqlM7fnpBZ0DPaH1PXfib RznSKaI+/jpymjugGYJQK8htPVla+sSsNt/UaxtL4aoi8eD80PvB6yq48cAzaSXZ sq8UzS3otQ4HYJNKxcjcGhHgdAArtRmWVeOsZoIanbE6JvkuDSm25kLPZQksMnuC o0SrmTdA0DhwlervSrWWKsd9qV8u+LoWsAaC9W10V8HnZBZpsZ7+Hj2m9Y3zzpJf EHenKjFFyPFJiJc4hrXfAGJ38Zeo4/bHrwlw+gCaIrMcEYiM3RJhyqE= =Cy9r -----END PGP SIGNATURE----- --=-fMvSnfjmTrA69X1R0RoU--