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