You are not logged in.

#1 2006-05-24 20:31:21

abrouwers
Member
Registered: 2006-05-15
Posts: 6

Pacman "clean up"

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

#2 2006-05-24 20:41:36

FUBAR
Member
From: Belgium
Registered: 2004-12-08
Posts: 1,029
Website

Re: Pacman "clean up"

List orphaned packages:

pacman -Qe

Remove package and its dependencies (without breaking other dependencies):

pacman -Rs foo

Learn more about this exciting tool you hear so much about:

man pacman
pacman --help
pacman -R --help
pacman -Q --help
you get the idea

A bus station is where a bus stops.
A train station is where a train stops.
On my desk I have a workstation.

Offline

#3 2006-06-19 23:57:32

skottish
Forum Fellow
From: Here
Registered: 2006-06-16
Posts: 7,942

Re: Pacman "clean up"

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

#4 2006-06-20 00:37:44

Cerebral
Forum Fellow
From: Waterloo, ON, CA
Registered: 2005-04-08
Posts: 3,108
Website

Re: Pacman "clean up"

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. smile

Offline

#5 2006-06-20 01:09:35

jaboua
Member
Registered: 2005-11-05
Posts: 634

Re: Pacman "clean up"

I always uninstall packages like this:

pacman -Rcs package

That 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

#6 2006-06-20 01:34:04

skottish
Forum Fellow
From: Here
Registered: 2006-06-16
Posts: 7,942

Re: Pacman "clean up"

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

#7 2006-06-20 01:36:49

Cerebral
Forum Fellow
From: Waterloo, ON, CA
Registered: 2005-04-08
Posts: 3,108
Website

Re: Pacman "clean up"

jaboua wrote:

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. wink

Offline

#8 2009-09-01 03:31:31

malachi
Member
Registered: 2008-11-11
Posts: 15

Re: Pacman "clean up"

Actually, man pacman states that the '-e' option filters output to explicit. Orphans are detected with -dt or --deps --unrequired

Offline

#9 2009-09-01 03:35:27

Allan
Pacman
From: Brisbane, AU
Registered: 2007-06-09
Posts: 11,672
Website

Re: Pacman "clean up"

yeah - but things have changed in the last three years...

See: http://wiki.archlinux.org/index.php/For … Bumping.27

Offline

Board footer

Powered by FluxBB