Apparently, though unproven, at 17:22 on Wednesday 08 December 2010, Helmut Jarausch did opine thusly:
> On 12/08/10 14:40:56, Matthew Summers wrote: > > On Wed, Dec 8, 2010 at 5:23 AM, Helmut Jarausch > > > > <jarau...@igpm.rwth-aachen.de> wrote: > > > Hi, > > > > > > does anybody know about an easy method to remove all entries from > > > /var/lib/portage/world > > > which would have been pulled in anyway > > > even if they were not contained in world. > > > > > > My current attempt would be to write a script > > > which executes emerge -vpc on each entry in world. > > > If it wouldn't be removed it's obsolete in world. > > > > > > Unfortunately this has to be done in several rounds. > > > > > > Many thanks for a hint, > > > Helmut. > > > > You may find that using 'emerge --deselect some-package' to be what > > you need. It removeds the file from your world file, but does not > > unmerge the package. That command switch is the functional opposite > > of > > --noreplace. > > > > I think you will find a wealth of information in the manpage for > > emerge. Happy reading! > > Sorry, but I still don't see it. > The main question is which packages might be removed > from 'world'? Your tools for this are two eyeballs and a brain. World gets bloated when users emerge libs and apps blindly that are covered by other packages and - meta ebuilds (avoid this with emerge -1) Edit the world file and remove everything you think might not be needed. Leave only apps you know for sure you need and want. Then run "emerge -p --depclean" which may or may not want to remove stuff. Inspect the list and add important stuff back into world with "emerge -n". Repeat until --depclean returns null output. eix-test-obsolete also gives useful clues about redundant world entries, but not in a clearly laid out section like you are after. I know of no app that does that. -- alan dot mckinnon at gmail dot com
