On 2020.12.06 16:04, Victor Ivanov wrote:
I'm on the same boat as Grant and, despite being fully up to date,
have found it incredibly infuriating to not be able to figure out why
I have so many python interpreters installed. I don't mind the
consumed space, but I get the itch from not knowing *why*.
On 06/12/2020 20:16, Neil Bothwick wrote:
emerge -cpv python:3.7 will show you what is keeping 3.7.
Thank you Neil for this amazing hack! This has truly been great at
solving the mystery.
Using this I finally found out that on my system the only thing
keeping Python 3.7 was:
app-office/libreoffice-bin-6.4.6.2-r2 requires
dev-lang/python:3.7[xml]
On that note, I feel like I should share my sentiment on what I had
tried before to solve this conundrum:
$ eix --installed-with-use python_targets_python3_7
$ eix --installed-with-use python_single_target_python7_7
but obviously the above only work for ebuilds that explicitly have
the respective PYTHON_TARGETS and PYTHON_SINGLE_TARGET variables and
will not include hard dependencies - this is to be expected.
More shockingly however, I was surprised that equery did not reveal
_anything_ useful at all e.g.
$ equery depends python:3.7
$ equery depends '=dev-lang/python:3.7'
$ eix --installed-depend python:3.7
eix above was also useless as it provided a very different output to
that of `emerge -cpv'. I thought the whole purpose of 'equery
depends <atom>' was to do exactly that - list any packages that
depend on the given atom. Or am I completely misunderstanding how the
above 3 work?!
My understanding was that "equery d" gives you a list from portage, not
caring about what is currently installed, where "emerge -pvc" will tell
you what is preventing the removal of the package.
