1 |
I'm on the same boat as Grant and, despite being fully up to date, have |
2 |
found it incredibly infuriating to not be able to figure out why I have |
3 |
so many python interpreters installed. I don't mind the consumed space, |
4 |
but I get the itch from not knowing *why*. |
5 |
|
6 |
On 06/12/2020 20:16, Neil Bothwick wrote: |
7 |
> emerge -cpv python:3.7 will show you what is keeping 3.7. |
8 |
|
9 |
Thank you Neil for this amazing hack! This has truly been great at |
10 |
solving the mystery. |
11 |
|
12 |
Using this I finally found out that on my system the only thing keeping |
13 |
Python 3.7 was: |
14 |
|
15 |
app-office/libreoffice-bin-6.4.6.2-r2 requires dev-lang/python:3.7[xml] |
16 |
|
17 |
On that note, I feel like I should share my sentiment on what I had |
18 |
tried before to solve this conundrum: |
19 |
|
20 |
$ eix --installed-with-use python_targets_python3_7 |
21 |
$ eix --installed-with-use python_single_target_python7_7 |
22 |
|
23 |
but obviously the above only work for ebuilds that explicitly have the |
24 |
respective PYTHON_TARGETS and PYTHON_SINGLE_TARGET variables and will |
25 |
not include hard dependencies - this is to be expected. |
26 |
|
27 |
More shockingly however, I was surprised that equery did not reveal |
28 |
_anything_ useful at all e.g. |
29 |
|
30 |
$ equery depends python:3.7 |
31 |
$ equery depends '=dev-lang/python:3.7' |
32 |
$ eix --installed-depend python:3.7 |
33 |
|
34 |
eix above was also useless as it provided a very different output to |
35 |
that of `emerge -cpv'. I thought the whole purpose of 'equery depends |
36 |
<atom>' was to do exactly that - list any packages that depend on the |
37 |
given atom. Or am I completely misunderstanding how the above 3 work?! |
38 |
|
39 |
- Victor |