1 |
On Sunday, 24 June 2018 10:35:37 BST Marc Joliet wrote: |
2 |
> Am Sonntag, 24. Juni 2018, 11:10:48 CEST schrieb Mick: |
3 |
> [snip] |
4 |
> |
5 |
> > Is the default python target determined by the profile and does this |
6 |
> > override choices through eselect? |
7 |
> > |
8 |
> > Should 'eselect python update' set 3.6 as the default when emerge seems to |
9 |
> > be determined to use 3.5? |
10 |
> > |
11 |
> > # eselect python list |
12 |
> > |
13 |
> > Available Python interpreters, in order of preference: |
14 |
> > [1] python3.6 |
15 |
> > [2] python3.5 |
16 |
> > [3] python3.4 (uninstalled) |
17 |
> > [4] python2.7 (fallback) |
18 |
> > |
19 |
> > While from emerge --info I get: |
20 |
> > |
21 |
> > PYTHON_SINGLE_TARGET="python3_5" PYTHON_TARGETS="python2_7 python3_5" |
22 |
> |
23 |
> The two are orthogonal: one determines for which versions of Python a |
24 |
> package is installed, the other manages the python{,2,3} symlinks. |
25 |
> |
26 |
> > I don't fancy rebuilding libreoffice + 67 more packages on 3 PCs just for |
27 |
> > grins. |
28 |
> |
29 |
> See bug #656406. If you don't care for going back (like me), you can do the |
30 |
> following (make.conf isn't enough because apparently that overrides, e.g., |
31 |
> asciidoc being forced to PYTHON_SINGLE_TARGET="python2_7"): |
32 |
> |
33 |
> % cat /etc/portage/profile/make.defaults |
34 |
> PYTHON_TARGETS="python2_7 -python3_5 python3_6" |
35 |
> PYTHON_SINGLE_TARGET="-python3_5 python3_6" |
36 |
|
37 |
|
38 |
Thank you Mark, I guessed the version update had been reversed, but hadn't |
39 |
seen the bug. |
40 |
|
41 |
-- |
42 |
Regards, |
43 |
Mick |