On Thu, 26 Jul 2018 17:34:25 +0300, Grand Duet wrote: > > FWIW I had no problem with the profile change and locked my system at > > 3.6 to save switching back when the profile did so. > > Ok. There was such a news. However, I have actually followed the > following recommendation in it, before the last python_target switch > from 3.5 to 3.6: > > If you would like to postpone the switch to Python 3.6, you can copy > the current value of PYTHON_TARGETS and/or PYTHON_SINGLE_TARGET > to /etc/portage/make.conf or its equivalent: > > PYTHON_TARGETS="python2_7 python3_5" > PYTHON_SINGLE_TARGET="python3_5" > > but the emerge gave strange errors mentioned above and aborted.
I got some message about USE flags when keeping it at 3.6 in the same way. So I did it in what seemed like the more elegant way of overriding a profile change, in /etc/portage/profile/make.defaults. PYTHON_TARGETS="python2_7 python3_5 -python3_6" PYTHON_SINGLE_TARGET="python3_5 -python3_6" -- Neil Bothwick Last words of a Windows user: = Where do I have to click now? - There?
pgpRfsaAtQmlL.pgp
Description: OpenPGP digital signature
