On 27/02/2016 22:27, »Q« wrote: > On Sat, 27 Feb 2016 21:40:06 +0200 > Alan McKinnon <alan.mckin...@gmail.com> wrote: > >> I don't know much about PYTHON_SINGLE_TARGET and PYTHON_TARGET, it all >> seemed to just work so I never looked further. Until now. Of all >> packages, libreoffice seems to want only python3: >> >> I can set it in make.conf but as expected that causes all manner of >> other packages to fail emerge checks as they need python2.7. >> >> What's the preferred way to deal with this situation? >> Some relevant info: >> >> !!! The ebuild selected to satisfy "app-office/libreoffice" has unmet >> requirements. >> - app-office/libreoffice-5.1.0.3::gentoo USE="bluetooth branding cups >> dbus gstreamer java kde mysql vlc (-aqua) -coinmp -collada -debug -eds >> (-firebird) -gltf -gnome -gtk -gtk3 -jemalloc -libressl -odk -postgres >> (-telepathy) -test" ABI_X86="64" LIBREOFFICE_EXTENSIONS="-nlpsolver >> -scripting-beanshell -scripting-javascript -wiki-publisher" >> PYTHON_SINGLE_TARGET="-python3_4 -python3_5" PYTHON_TARGETS="python3_4 >> python3_5" >> >> The following REQUIRED_USE flag constraints are unsatisfied: >> exactly-one-of ( python_single_target_python3_4 >> python_single_target_python3_5 ) > >> khamul ~ # eselect python list >> Available Python interpreters: >> [1] python2.7 >> [2] python3.4 >> [3] python3.5 * > > I think you can just put > > app-office/libreoffice python_single_target_python3_5 > > into package.use, which is easier than messing with package.env.
Yup, that's the way it seems. Also it looks like it'll be the way for at least the next 10 years - that's my minimum guess how long I reckon python-2 will be around -- Alan McKinnon alan.mckin...@gmail.com
