1 |
On Sun, Oct 27 2013, Mike Gilbert wrote: |
2 |
|
3 |
> Making things "just work" is complex when trying to juggle 6 or more |
4 |
> supported versions/implementations of python. |
5 |
|
6 |
Indeed. |
7 |
|
8 |
> We have tried to explain the magic make.conf lines in the Python user guide. |
9 |
> |
10 |
> https://www.gentoo.org/proj/en/Python/python-r1/user-guide.xml |
11 |
> |
12 |
> We also try to make sure that most users never have to touch |
13 |
> PYTHON_TARGETS, etc; the default values provided by your profile are |
14 |
> set up to allow *stable* python2.7 and python3.2 to work properly. |
15 |
|
16 |
> ~arch users are expected to read the docs. ^_^ |
17 |
|
18 |
I am a ~amd64 user and I just read the user-guide. :-) |
19 |
I do not see any action items for my system; but do see a large number |
20 |
of reinstalls proposed by emerge |
21 |
|
22 |
I do not change any python variables in make.conf so emerge --info shows |
23 |
PYTHON_SINGLE_TARGET="python2_7" |
24 |
PYTHON_TARGETS="python2_7 python3_2" |
25 |
|
26 |
a recursive grep -i for python in /etc/portage yields only |
27 |
./package.use/imaging-pillow:5:virtual/python-imaging -python_targets_python3_2 |
28 |
|
29 |
So I basically have the default except for the imaging/pillow business. |
30 |
|
31 |
I note that update world wants to rebuild a bunch of packages (the |
32 |
entire output is below). Some are qt-related others involve |
33 |
PYTHON_TARGETS. |
34 |
|
35 |
Does this mean that I can let the 44 packages / 38 reinstalls update occur |
36 |
and expect a running system to result? It is unusual, but I realize not |
37 |
unprecedented, to have so many reinstalls and I would like to confirm |
38 |
that this is expected. |
39 |
|
40 |
thanks, |
41 |
allan |