Gentoo Archives: gentoo-user

From: Helmut Jarausch <jarausch@××××××××××××××××.de>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] How to get rid of Python2 (where possible)
Date: Sat, 29 Mar 2014 10:45:57
Message-Id: 1396089946.6520.0@numa-i.igpm.rwth-aachen.de
In Reply to: Re: [gentoo-user] How to get rid of Python2 (where possible) by Tom Wijsman
1 On 03/28/2014 08:29:27 PM, Tom Wijsman wrote:
2 > On Fri, 28 Mar 2014 11:42:59 +0100
3 > Helmut Jarausch <jarausch@××××××××××××××××.de> wrote:
4 >
5 > > sys-apps/portage:0
6 > >
7 > > (sys-apps/portage-9999:0/0::gentoo, ebuild scheduled for merge)
8 > > pulled in by
9 > > sys-apps/portage (Argument)
10 > >
11 > > (sys-apps/portage-9999:0/0::gentoo, installed) pulled in by
12 > >
13 > > sys-apps/portage[**SNIP**] required by
14 > > (app-portage/gentoolkit-dev-0.2.8.3-r1:0/0::gentoo, installed)
15 > >
16 > > sys-apps/portage[**SNIP**] required by
17 > > (app-admin/webapp-config-1.53:0/0::gentoo, installed)
18 > >
19 > > sys-apps/portage[**SNIP**] required by
20 > > (app-portage/flaggie-0.2.1:0/0::gentoo, installed)
21 >
22 > The thing with Python is that it wants 'packages that support Python'
23 > depend on 'Python packages that have the same versions supported'.
24 >
25 > Iotw, from the above example; let's say the reverse dependencies
26 > gentoolkit-dev, webapp-config, flaggie, ... were build with 2.x and
27 > with 3.x, they would want both 2.x and 3.x set on sys-apps/portage.
28 >
29 > If you drop 2.x you can't just rebuild Portage, you'll need to rebuild
30 > the reverse deps as well; such that they no longer want 2.x on
31 > Portage.
32 >
33 > So, when changing PYTHON_TARGET in make.conf; you will want to do
34 > something along the lines of `emerge -auvDN @world --backtrack=9001`,
35 > this to ensure that the reverse dependencies of Portage no longer
36 > depend on Portage having the previously set Python versions.
37 >
38 > Portage will then go ahead and rebuild both Portage and its reverse
39 > dependencies; that way, it doesn't create the conflict you saw.
40 >
41 > (Backtracking 9001 so it is sufficiently high to not cause conflicts)
42 >
43 > --
44
45 Unfortunately, this doesn't solve my problem.
46
47 If I remove python2_7 from PYTHON_TARGET emerge -auvDN @world
48 --backtrack=9001
49 fails for those packages which don't support Python3.
50
51 But if I keep python2_7 in PYTHON_TARGET then all packages which support
52 Python2_7 and Python3_3 are installed twice, once in
53 /usr/lib64/python2.7
54 and then in /usr/lib64/python3.3
55
56 But I'm looking for a means to install packages which do support
57 Python3.3
58 only for Python3.3 and which installs packages which don't support
59 Python3.3
60 nevertheless under /usr/lib64/python2.7
61
62 Helmut

Replies

Subject Author
Re: [gentoo-user] How to get rid of Python2 (where possible) Tom Wijsman <TomWij@g.o>