Difference between revisions of "News:Python Multiplexing(And another Ego update)"
(Created page with "{{News |Summary=An update to ego-1.1.3-r5 |News Format=Extended |Author=Oleg |Publication Status=Published |Publication Date=2017/08/25 }} As many may noticed with recent meta...") |
|||
| Line 11: | Line 11: | ||
{{console|body= | {{console|body= | ||
# ##i## ego sync | # ##i## ego sync | ||
# ##i## emerge -1 --nodeps ego | # ##i## USE="python_single_target_python3_4 python_targets_python3_4" emerge -1 --nodeps ego | ||
# ##i## epro update | # ##i## epro update | ||
}} | }} | ||
{{fancynote|It is needed to set python_single_target_python3_4 and python_targets_python3_4 useflags temporarily to be able to upgrade ego.}} | |||
Latest revision as of 04:19, October 9, 2017
Python Multiplexing(And another Ego update)
As many may noticed with recent meta-repo updates a difficulty with PYTHON_TARGETS appeared due to new python multiplexing functionality in app-admin/ego has landed into meta-repo. This happened little bit too early than planned, hence the unexpected surprise. In a few words, python multiplexing is the new way of PYTHON_TARGETS handle. Previously python variables were hardcoded in profiles's make.defaults with ability to override in /etc/portage/make.conf. Now meta-repo scripts automatically set the required python settings. This functionality also coupled with kits and python version updates, which can be performed in one step. More on this will be added in future news items.
The fix is following:
root # ego sync root # USE="python_single_target_python3_4 python_targets_python3_4" emerge -1 --nodeps ego root # epro update
It is needed to set python_single_target_python3_4 and python_targets_python3_4 useflags temporarily to be able to upgrade ego.