From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 19D03138010 for ; Mon, 3 Sep 2012 21:12:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A13A121C0D7; Mon, 3 Sep 2012 21:12:23 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 03A2F21C0D7 for ; Mon, 3 Sep 2012 21:12:22 +0000 (UTC) Received: from mail-we0-f181.google.com (mail-we0-f181.google.com [74.125.82.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id DB77233C387 for ; Mon, 3 Sep 2012 21:12:21 +0000 (UTC) Received: by weyt57 with SMTP id t57so853020wey.40 for ; Mon, 03 Sep 2012 14:12:19 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Discussions centering around the Python ecosystem in Gentoo Linux X-BeenThere: gentoo-python@gentoo.org X-BeenThere: gentoo-python@lists.gentoo.org MIME-Version: 1.0 Received: by 10.216.24.140 with SMTP id x12mr11026526wex.101.1346706739074; Mon, 03 Sep 2012 14:12:19 -0700 (PDT) Received: by 10.223.2.131 with HTTP; Mon, 3 Sep 2012 14:12:18 -0700 (PDT) In-Reply-To: <20120902210221.2166c1e9@pomiocik.lan> References: <5015EDC2.202@gentoo.org> <50295078.7030104@gentoo.org> <50434F32.7070303@gentoo.org> <20120902193405.1700f85f@pomiocik.lan> <20120902210221.2166c1e9@pomiocik.lan> Date: Mon, 3 Sep 2012 17:12:18 -0400 Message-ID: Subject: Re: [gentoo-python] Python 3 in Gentoo From: Mike Gilbert To: gentoo-python@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: b9f8742e-1a98-4d78-8f34-06baae0054bb X-Archives-Hash: cd28b1b73dde53ecaab823f660256881 On Sun, Sep 2, 2012 at 3:02 PM, Micha=C5=82 G=C3=B3rny = wrote: > On Sun, 2 Sep 2012 13:54:13 -0400 > Mike Gilbert wrote: > >> On Sun, Sep 2, 2012 at 1:34 PM, Micha=C5=82 G=C3=B3rny >> wrote: >> > On Sun, 2 Sep 2012 13:16:38 -0400 >> > Mike Gilbert wrote: >> > >> >> On Sun, Sep 2, 2012 at 8:21 AM, Thomas Sachau >> >> wrote: >> >> > Mike Gilbert schrieb: >> >> >> On Mon, Aug 13, 2012 at 3:38 PM, Dirkjan Ochtman >> >> >> wrote: >> >> >>> On Mon, Aug 13, 2012 at 9:07 PM, Richard Yao >> >> >>> wrote: >> >> >>>>> Does this seem like a viable option? Is anyone going to >> >> >>>>> volunteer to take it from here? >> >> >>>> >> >> >>>> I can try to make time to make these changes this weekend if >> >> >>>> everyone is fine with that. >> >> >>> >> >> >>> I think we should inform gentoo-dev first. >> >> >>> >> >> >> >> >> >> Just in case someone is waiting for me to take some further >> >> >> actions on this, please don't wait on me. I really don't have >> >> >> the motivation to carry this plan any further. >> >> >> >> >> >> If someone else wants to carry the torch, I am happy to assist. >> >> >> >> >> >> >> >> > >> >> > Just to get the right summary: >> >> > >> >> > The plan is now to replace all dependencies in ebuilds, which >> >> > have either "dev-lang/python" or something like >> >> > ">=3Ddev-lang/python-X.Y" to use "virtual/python" instead? >> >> > >> >> >> >> That's right. >> >> >> >> > What about versioned dependencies exluding python versions still >> >> > in the main tree like ">=3Ddev-lang/python-2.7"? >> >> > >> >> >> >> In this case the virtual would not work. Instead, it could be >> >> replaced with this: >> >> >> >> || ( =3Ddev-lang/python-2.7* =3Ddev-lang/python-3* ) >> >> >> >> Similarly, >=3Ddev-lang/python-2.6 could be replaced with this: >> >> >> >> || ( =3Ddev-lang/python-2.7* =3Ddev-lang/python-2.6* >> >> =3Ddev-lang/python-3* ) >> > >> > You could go with virtual/python-2.7, -2.6, -2.5 being an >> > appropriate minimal version. >> > >> >> I gave that idea some thought, but I think it would be a somewhat >> confusing (it makes my head hurt). >> >> There are actually a few ways I could see a versioned virtual being >> implemented; can you articulate exactly what each virtual version >> would have in RDEPEND and how it would be used in other ebuilds? > > Well, one not-so-crazy idea is that we have: > > virtual -2.5, SLOT=3D"2.5+": || ( =3Dpython-2* =3Dpython-3* ) > virtual -2.6, SLOT=3D"2.6+": || ( python:2.7 python:2.6 =3Dpython-3* ) > virtual -2.7, SLOT=3D"2.7+": || ( python:2.7 =3Dpython-3* ) > > # optioanlly, I think it may be nicer than =3Dpython-3* in ebuilds > virtual -3.1, SLOT=3D"3.1+": =3Dpython-3* > > It's a bit hacky but with it, you can then do: > > RDEPEND=3D"virtual/python:2.6+" > > which is quite self-explanatory. > That could work. In this case, we would need to ensure that ebuilds do not depend on virtual/python without a slot (or version wildcard).