to query all those packages with no dependent?

[guyuming]

background:

https://forums.gentoo.org/viewtopic-t-1158257-highlight-.html
https://forums.gentoo.org/viewtopic-t-1158521-highlight-.html

i had unpacked stage3 on existing system by mistake.
and i had run something like

[szatox]

[NeddySeagoon]

guyuming,

There are a few world cleaning scripts on the wiki.
There is cleaning the world file (wiki) - check the script too.

Its only an advisory as its not an error to have more than the bare minimum in your world file.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[dmpogo]

Honestly, I just clean the /var/lib/portage/world with ordinary editor like vi

[NeddySeagoon]

dmpogo,

emerge --deselect is designed for that.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[guyuming]

I run the query to generate /tmp/WorldDeselect

[axl]

Uhm, I think when he unpacked a stage 3, world file was overwrited. So now, there's a tone of dangling packages that are not part of world and should be depcleaned. Also, probably @system is consistent, but @world isn't. We can also prolly assume make.conf lost a bunch of USE flags.

First thing first. I think you should start with trying to restore USE flags as close to the original as possible.

Second thing, should work to repopulate world file. You do not need to add every other dependency, but the big things have to be in world. For instance, you do not need to add xorg-drivers, and every other driver, or X for that matter, but you do prolly need to add at least the window managers you used. Something like gnome, or kde-meta or whatever you use, will prolly be enough. So what I would do is "emerge --depclean --pretend", and start selecting from there, the big things. The things that were in @world before. It will take to run the same thing a few times, and then just add them with a text editor in world file. You don't actually need to compile them, just add them. For now.

Third, update. There could be inconsistencies. Dependencies broken at the level of @world (not system). Meaning gcc/glibc/binutils all came from stage3, and are ok with each other, but that doesn't mean one of the binaries from @world isn't dependent on a newer glibc for instance and it's broken atm. So after you are happy with a relatively large enough world file, you should do emerge -NuavD --with-bdeps=y @world. Let that finish.

And then to finish, revdep-rebuild should find those packages that are still broken and that have inconsistencies, and then to top it all off, you could do equery k \* (equery is part of gentoolkit) which should tell you which packages have changed files since they were installed.

That's what I would do.

[Genone]

[szatox]

[NeddySeagoon]

guyuming,

xorg-drivers should be pulled in by your VIDEO_CARDS and INPUT_DEVICES in make.conf.

The entries there will decide which x11-drivers/xf86-video-* and x11-drivers/xf86-input-* will be retained.
If you don't know what x11-drivers/xf86-video-dummy is for, you don't need it.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[guyuming]

@NeddySeagoon, thanks!

turned out my assumption that portage package is organized as DAG(directed acyclic graph) is NOT correct.

There are cycles in dependency.

for example, app-editors/emacs and app-editors/emacs depends on each other, so if i emerge --depclean any of them alone, it won't be removed. But if i emerge --depclean both of them in a single command, both will be removed.

[NeddySeagoon]

guyuming,

That's why portage complains about circular dependencies from time to time. :)
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.