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