| 1 |
Howdy, |
| 2 |
|
| 3 |
Looking at the openshot ebuild, I see:: |
| 4 |
EAPI=6 |
| 5 |
PYTHON_COMPAT=( python3_{4,5} ) |
| 6 |
|
| 7 |
among other interesting details. |
| 8 |
|
| 9 |
So it should work with python 3.4 or 3.5, right? |
| 10 |
|
| 11 |
I have this:: |
| 12 |
Installed versions: 2.7.10-r1 3.4.3-r1 |
| 13 |
(examples gdbm ipv6 ncurses readline sqlite ssl threads tk wide-unicode xml |
| 14 |
-berkdb -build -doc -hardened -wininst ELIBC="-uclibc") |
| 15 |
|
| 16 |
Available Python interpreters: |
| 17 |
[1] python2.7 |
| 18 |
[2] python3.4 * |
| 19 |
|
| 20 |
|
| 21 |
currently I get this build failure message:: |
| 22 |
|
| 23 |
The ebuild selected to satisfy "=media-video/openshot-2.0.6" has unmet |
| 24 |
requirements. |
| 25 |
- media-video/openshot-2.0.6::gentoo USE="" ABI_X86="64" |
| 26 |
PYTHON_SINGLE_TARGET="-python3_4 -python3_5" PYTHON_TARGETS="python3_4 |
| 27 |
-python3_5" |
| 28 |
|
| 29 |
The following REQUIRED_USE flag constraints are unsatisfied: |
| 30 |
exactly-one-of ( python_single_target_python3_4 |
| 31 |
python_single_target_python3_5 ) |
| 32 |
|
| 33 |
The above constraints are a subset of the following complete expression: |
| 34 |
exactly-one-of ( python_single_target_python3_4 |
| 35 |
python_single_target_python3_5 ) python_single_target_python3_4? ( |
| 36 |
python_targets_python3_4 ) python_single_target_python3_5? ( |
| 37 |
python_targets_python3_5 ) |
| 38 |
|
| 39 |
|
| 40 |
So, I should not have to install python 3.5. But that's no big deal. |
| 41 |
If I do install python 3.5, it'll have it's own slot and I should leave |
| 42 |
python-3.4x as the default or can I set the default to 3.5x? Not sure what I |
| 43 |
missed. |
| 44 |
|
| 45 |
|
| 46 |
discussion or guidance is welcome, |
| 47 |
James |
Archives