From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NqBnH-0002y6-D1 for garchives@archives.gentoo.org; Fri, 12 Mar 2010 20:49:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C1ACDE0969; Fri, 12 Mar 2010 20:49:08 +0000 (UTC) Received: from ironclad.mail.utexas.edu (ironclad.mail.utexas.edu [146.6.25.7]) by pigeon.gentoo.org (Postfix) with ESMTP id 0B8F6E0960 for ; Fri, 12 Mar 2010 20:48:54 +0000 (UTC) X-IronPort-MID: 22107839 Received: from wb2-a.mail.utexas.edu ([128.83.126.136]) by ironclad.mail.utexas.edu with SMTP; 12 Mar 2010 14:48:55 -0600 Received: (qmail 23423 invoked from network); 12 Mar 2010 20:48:54 -0000 Received: from cpe-72-179-53-114.austin.res.rr.com (HELO ?192.168.1.116?) (rpinjala@72.179.53.114) by wb2.mail.utexas.edu with (RC4-MD5 encrypted) ESMTPSA; 12 Mar 2010 20:48:54 -0000 Message-ID: <4B9AA8B6.1030208@p-static.net> Date: Fri, 12 Mar 2010 14:48:54 -0600 From: Ravi Pinjala User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100309 Thunderbird/3.0.3 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 MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: Python 3.1: Stabilization and news item References: <201003041923.17749.Arfrever@gentoo.org> <4B919F98.2090208@gentoo.org> <20100308212816.GA1309@linux1> <201003101837.02887.Arfrever@gentoo.org> In-Reply-To: <201003101837.02887.Arfrever@gentoo.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Archives-Salt: b401b87d-95af-465f-8fb2-d10949b4cecc X-Archives-Hash: f4f6ae0f53121d46e18f6dcc06b09488 On 03/10/10 11:36, Arfrever Frehtes Taifersar Arahesis wrote: > 2010-03-08 22:28:16 William Hubbs napisa=C5=82(a): >> On Fri, Mar 05, 2010 at 04:19:36PM -0800, Zac Medico wrote: >>> No, it won't. To prove it, I've just tested with a stable stage3 >>> containing portage-2.1.7.x. Here are the steps: >>> >>> 1) extract stable stage3 and chroot into it >>> 2) mkdir /etc/portage&& echo "dev-lang/python ~*">> >>> /etc/portage/package.keywords >>> 3) Run `emerge -pu --deep=3D1 portage`: >>> These are the packages that would be merged, in order: >>> >>> Calculating dependencies... done! >>> [ebuild UD] sys-apps/sandbox-1.6-r2 [2.2] >>> [ebuild UD] app-shells/bash-4.0_p35 [4.0_p37] >>> [ebuild U ] dev-lang/python-2.6.4-r1 [2.6.4] >>> >>> If you try `emerge -puD world` then you will see >>> dev-lang/python-3.1.1-r1 pulled in by the unspecific dev-lang/python >>> atoms in the cracklib and libxml2 dependencies. However, in >>> portage-2.1.7.x (current stable), there is support for >>> pseudo-version-ranges in dependencies. This allows you use a >>> dependency like>> python3, and that will prevent it from getting pulled into the >> >> According to this, we can fix all of the dependencies in the tree then >> stabilize python3 without having any issues, so I would vote for this >> route, because it still oinsures that the stable tree will work >> together. > > Almost everybody has at least 1 package installed which supports both P= ython 2 > and Python 3 and depends on dev-lang/python without version specificati= on, > so Python 3 would be pulled into dependency graph, so fixing of depende= ncies > doesn't need to block stabilization of Python 3. > What about introducing a python3 USE flag? Seems like that would keep=20 everybody happy. --Ravi