| 1 |
On Thu, 26 Jul 2018 17:34:25 +0300, Grand Duet wrote: |
| 2 |
|
| 3 |
> > FWIW I had no problem with the profile change and locked my system at |
| 4 |
> > 3.6 to save switching back when the profile did so. |
| 5 |
> |
| 6 |
> Ok. There was such a news. However, I have actually followed the |
| 7 |
> following recommendation in it, before the last python_target switch |
| 8 |
> from 3.5 to 3.6: |
| 9 |
> |
| 10 |
> If you would like to postpone the switch to Python 3.6, you can copy |
| 11 |
> the current value of PYTHON_TARGETS and/or PYTHON_SINGLE_TARGET |
| 12 |
> to /etc/portage/make.conf or its equivalent: |
| 13 |
> |
| 14 |
> PYTHON_TARGETS="python2_7 python3_5" |
| 15 |
> PYTHON_SINGLE_TARGET="python3_5" |
| 16 |
> |
| 17 |
> but the emerge gave strange errors mentioned above and aborted. |
| 18 |
|
| 19 |
I got some message about USE flags when keeping it at 3.6 in the same |
| 20 |
way. So I did it in what seemed like the more elegant way of overriding a |
| 21 |
profile change, in /etc/portage/profile/make.defaults. |
| 22 |
|
| 23 |
PYTHON_TARGETS="python2_7 python3_5 -python3_6" |
| 24 |
PYTHON_SINGLE_TARGET="python3_5 -python3_6" |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Neil Bothwick |
| 29 |
|
| 30 |
Last words of a Windows user: = Where do I have to click now? - There? |
Archives