On Sun, 3 May 2020 08:37:27 -0400 Brian Evans <grkni...@gentoo.org> wrote:
> On 5/3/20 2:58 AM, Fabian Groffen wrote: > > On 02-05-2020 23:24:42 -0700, Brian Dolbec wrote: > >> On Sun, 3 May 2020 07:28:50 +0200 > >> Viktar Patotski <xp.vit....@gmail.com> wrote: > >> > >>> Hi all, > >>> > >>> I'd also like to clean my system and have it Python 2.7 free. Are > >>> there any guidelines to check which packages are still using > >>> pyton2_7 in my system? > >>> > >>> Thanks, > >>> Viktar > >>> > >> > >> There are both equery and enalyze commands in gentoolkit that can > >> give you reports about what pkgs are installed. > >> > >> equery hasuse > >> enalyze analyze [use|pkguse] > >> > >> for help on them: > >> equery -h > >> equery hasuse -h > >> enalyze -h > >> enalyze a -h > > > > In addition to these great tools, portage-utils' quse might also be > > useful: > > > > % quse python2_7 > > ... > > > > > > Thanks, > > Fabian > > > > All of the mentioned tools will show if packages have the flag but not > necessarily have it active. Not True: enalyze does strictly installed pkgs analysis, plus has the ability to rebuild package.accept_keywords and package.use files after profile changes or disaster (file loss, etc) > > eix has an option to search the active flag: > > eix --installed-with-use <flag> > > However, this still skips build-time dependencies that may keep python > 2.7 around. > > The most accurate way to see what's tied to python 2.7 is to pretend > to remove it: > emerge -pvc dev-lang/python:2.7 > > Brian >
