On 12/09/2019 10:56, Philip Webb wrote:
I'm now left with 5 problem pkgs :
llvm-7.1.0 fetchmail-6.3.26-r4 qtwebkit-5.212.0_pre20180120
spidermonkey-60.5.2_p0-r2 firefox-60.8.0
the former 3 all have in their ebuilds
PYTHON_COMPAT=( python2_7 )
the latter 2 are said to require
python 2.7 : 2.7 [ncurses sqlite ssl threads]
I don't understand the list in square brackets, which are USE flags :
they aren't set in 'make.conf' or elsewhere AFAIK.
Can anyone explain (1) how to get around the 1st 3 ebuilds
or (2) what the problem is with the 2nd 2 examples ?
The square brackets tell portage that the package needs python emerged
with those USE flags set on the python ebuild.
As for getting around the first 3, you need to uninstall everything that
depends on them and then unmerge them. I don't know how feasible that
is, because some important packages probably depend on LLVM? Not sure.
Right now, Python 2.7 is required for a useful desktop machine because
important packages like Mesa probably depend on something that in turn
uses Python 2.7. For a minimal system without X11 though you can
probably do it.
