You are not logged in.
Pages: 1
Topic closed
Just out of curiosity...say I install a media player that has a ton of deps, and later find that I dislike it. So, I remove it using pacman, but it will only remove that one package, leaving the useless deps behind.
Is there any way to search my system for orphaned packages like this?
Thanks,
Andrew
Offline
List orphaned packages:
pacman -QeRemove package and its dependencies (without breaking other dependencies):
pacman -Rs fooLearn more about this exciting tool you hear so much about:
man pacman
pacman --help
pacman -R --help
pacman -Q --help
you get the ideaA bus station is where a bus stops.
A train station is where a train stops.
On my desk I have a workstation.
Offline
I have a question about this:
All of the orphaned packages are simply the original tar.gz files and have no relationship to the currently installed software? I guess I'm asking, can they all safely be deleted?
Offline
From man pacman:
-e, --orphans
List all packages that were explicitly installed (ie, not pulled in as a dependency by other packages) and are
not required by any other packages.That pretty concisely explains what orphans are.
man is your friend. ![]()
Offline
I always uninstall packages like this:
pacman -Rcs packageThat also removes unneeded deps.
Also look here:
http://bbs.archlinux.org/viewtopic.php?t=22360
Cerebral: I always thought it was opposite - that orphans were packages pulled in as dependencies, but weren't required anymore. I'd say that it fits with the wikipedia description as well ("a child that has lost it's parents" - I think of the explicitly installed packages as parents)
Offline
Thanks for the replies and the script. I asked because the files listed by pacman -Qe are all the files in the cache. I thought it was strange that I even have those still. There was 566MBs worth of stuff just hanging around inside doing nothing and this build isn't three days old yet!
Anyway, the orphan script produces three files that I can't un-install with the above listed command(s). pacman -Rcs <package> just throws an error saying that <package> isn't in the database.
Offline
Cerebral: I always thought it was opposite - that orphans were packages pulled in as dependencies, but weren't required anymore. I'd say that it fits with the wikipedia description as well
*shrug* He asked, in the context of pacman, what is considered an orphan. I never designed the system, I'm just explaining it. ![]()
Offline
Actually, man pacman states that the '-e' option filters output to explicit. Orphans are detected with -dt or --deps --unrequired
Offline
yeah - but things have changed in the last three years...
Offline
Pages: 1
Topic closed