On 24/03/2016 18:35, James wrote:
> Howdy,
>
> Looking at the openshot ebuild, I see::
> EAPI=6
> PYTHON_COMPAT=( python3_{4,5} )
>
> among other interesting details.
>
> So it should work with python 3.4 or 3.5, right?
Not quite.
IIRC PYTHON_COMPAT is the old way
PYTHON*_TARGET_* is the new way
>
> I have this::
> Installed versions: 2.7.10-r1 3.4.3-r1
> (examples gdbm ipv6 ncurses readline sqlite ssl threads tk wide-unicode xml
> -berkdb -build -doc -hardened -wininst ELIBC="-uclibc")
>
> Available Python interpreters:
> [1] python2.7
> [2] python3.4 *
>
>
> currently I get this build failure message::
>
> The ebuild selected to satisfy "=media-video/openshot-2.0.6" has unmet
> requirements.
> - media-video/openshot-2.0.6::gentoo USE="" ABI_X86="64"
> PYTHON_SINGLE_TARGET="-python3_4 -python3_5" PYTHON_TARGETS="python3_4
> -python3_5"
There's your problem.
PYTHON_SINGLE_TARGET is not set but the ebuild requires it (see
following error)
>
> The following REQUIRED_USE flag constraints are unsatisfied:
> exactly-one-of ( python_single_target_python3_4
> python_single_target_python3_5 )
>
> The above constraints are a subset of the following complete expression:
> exactly-one-of ( python_single_target_python3_4
> python_single_target_python3_5 ) python_single_target_python3_4? (
> python_targets_python3_4 ) python_single_target_python3_5? (
> python_targets_python3_5 )
>
>
> So, I should not have to install python 3.5. But that's no big deal.
> If I do install python 3.5, it'll have it's own slot and I should leave
> python-3.4x as the default or can I set the default to 3.5x? Not sure what I
> missed.
>
>
> discussion or guidance is welcome,
Add PYTHON_SINGLE_TARGET="python3_4" to USE for this package.
This might be an ebuild bug (python packages should have all been fixed
by now), or maybe it's on your end.
What do you have for
emerge --info | grep PYTHON
--
Alan McKinnon
[email protected]
