In a previous message, Fabian wrote:
The packages that are in "c" but not in "b" are not needed for any dependency and can thus be uninstalled. After thess packages have been uninstalled the script has to be run again
Except that, as someone has already said, this would end up listing all top-level packages - i.e. the ones you actually use - because nothing depends on them. This gives you still quite a hefty job for manually going through this list. It's probably just easier going through the list in YaST and trying to uninstall something - if YaST doesn't warn you, you're OK deleting it (provided the description shows it doesn't do anything important!). Also, for clarity, can anyone confirm that the 8.1 version of YaST handles this automatically if you use it to do all uninstallations? That is, there should never be orphan packages if YaST is used to uninstall? I'm still not sure whether someone has found orphan packages after using YaST or not. John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Fields of Valour: 2 Norse clans battle on one of 3 different boards