> > I am trying to determine what packages are actually in use on my > system and which are not[1]. ... > > 1. with the MDK library naming policy this becomes a requirement > because as a new version of a library becomes more and more used > by other packages on the system, the old library hangs around and > eventually becomes unused. >
I did it just yesterday. I just assumed that after I did urpmi --auto-select any package not contained in urpmi database is obsolete. So I did just [root@cooker root]# for i in $(rpm -qa) > do > zcat /var/lib/urpmi/synthesis.* | grep @info@ | grep -q $i || echo $i > done I gave me plenty of obsolete libraries, several non-existing packages like xine (which seemingly was renamed) and a couple of unofficial packages lik XFree86 from flepied. Works nicely must I say. Here is what I get on another system: [root@cooker root]# for i in $(rpm -qa) > do > zcat /var/lib/urpmi/synthesis.* | grep @info@ | grep -q $i || echo $i > done lm_utils-2.4.10_2.6.1-2mdk libgtkhtml18-0.15.0-2mdk XFree86-devel-4.1.99.4-1mdk XFree86-75dpi-fonts-4.1.99.4-1mdk VMwareWorkstation-3.0.0-1455 libcapplet0-1.5.8-2mdk libpng2-1.0.12-2mdk XFree86-libs-4.1.99.4-1mdk XFree86-xfs-4.1.99.4-1mdk XFree86-100dpi-fonts-4.1.99.4-1mdk XFree86-cyrillic-fonts-4.1.99.4-1mdk libdb3.2-3.2.9-3mdk libpython2.1-2.1.1-5mdk libgal15-0.15-2mdk libgtkhtml19-0.16.1-1mdk XFree86-4.1.99.4-1mdk XFree86-server-4.1.99.4-1mdk Catches obsolete libraries just fine. -andrej
