Arch Linux

farresito

Member

Registered: 2011-09-11

Posts: 2

Pacman Package Removing

Hi guys,

I have recently installed ArchLinux and was wondering how do you keep your system clean while installing and removing packages, because today I removed my Ruby package and saw that I still had my Ruby folder in /usr/lib with the gems, which logically is not installed by Pacman. Instead of, they are installed by a program that comes with Ruby.

Do you guys have any command which 'recursively' deletes all the folders and files installed by a package? I know there's a command which deletes recursively all the dependencies, but thats not what im looking for.

I dont know if I explained my problem properly. Apologizes for my english.

Regards!

gregor

Member

From: /planet/tmpfs

Registered: 2011-06-20

Posts: 175

Re: Pacman Package Removing

sudo pacman -Rcs 'package-name'

For recursively removing orphans :

sudo pacman -Rs $(pacman -Qtdq)

---

Archlinux (less = more)    + wmfs2-git

https://github.com/xorg62/wmfs/wiki

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: Pacman Package Removing

You installed stuff outside of pacman's control, so you can't reasonably expect pacman to manage its removal. The best solution is to install everything with pacman - if you can't or won't do this, you will need to find a way to manage your non-pacman stuff yourself.

farresito

Member

Registered: 2011-09-11

Posts: 2

Re: Pacman Package Removing

Thanks to both, guys. Really appreciate your answers.

@tomk: Its not that I install outside of pacman. I never install outside of pacman, but in that case I thought, as gem its part of ruby, that pacman would delete gem and, consequently, gem would delete what he aparently installed, being recursively, if that can be said so. Anyway, I will try to avoid this type of situations.

ngoonee

Forum Fellow

From: Between Thailand and Singapore

Registered: 2009-03-17

Posts: 7,362

Re: Pacman Package Removing

Thanks to both, guys. Really appreciate your answers.

@tomk: Its not that I install outside of pacman. I never install outside of pacman, but in that case I thought, as gem its part of ruby, that pacman would delete gem and, consequently, gem would delete what he aparently installed, being recursively, if that can be said so. Anyway, I will try to avoid this type of situations.

To explain a bit, pacman simply deletes the files that exist in the installed package. If the package (when run) creates a file, pacman does not know about it (pacman does not monitor what the binaries actually do). This is also the reason why (for example) firefox can create a profile which doesn't get deleted when you uninstall firefox.

---

Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.