removing unwanted programs

[geraldw321]

hello there  ,  if i want to remove programs i dont want or need , would i just use synaptic  to remove them ??  or is there a better way ?  and after removal  would i need to run a cleaner like bleachbit or dupe cleaner ?


thank you group 


PS this group is one of the best ive ever seen you are there quickly with a response and thorough and nice about it .it
makes me  proud to be a PCLOS user/supporter

[Just17]

Yes, Synaptic is the method to use when installing or removing programs.

[Rudge]

Be aware of what you remove. Removing "some" programs can remove libraries or other things that "desirable" programs use.

Just be careful about it. You should get "fair warning".

* Ha! Van Halen hehe *

[Yankee]

In hindsight,

Synaptic history can help if removing programs when programs are
installed one at a time.

You can tell what was installed for each.    Hasn't hurt my uninstalls
at a future date.

[johnmart]

In my experience Synaptic will warn you if you are removing a program that affects another. This especially happens if you use  the *complete removal* feature. --use with care--
A good rule of thumb **read error messages** :-)

[Bald Brick]

The problem with removing packages is that everything that was installed together with a package isn't necessarily removed with the package. So you may have to do some cleanup afterwards.

In other words:

If the package "foo" needs the package "bar" to work, you cannot uninstall "bar" without also uninstalling "foo". But the opposite is not true: you can uninstall "foo" without uninstalling "bar", even if "bar" was just installed as a dependency of "foo". This makes sense as other packages may also depend on "bar". So to get rid of everything that came with "foo" you may have to uninstall a few other packages separately.

Also note that configuration files are not always automatically uninstalled when you uninstall the package they belong to. If "foo" creates a directory .foo in your home folder, that directory will not be removed when you uninstall "foo". "Complete Removal" is often thought to mean that the configuration files are also removed, but with Synaptic in PCLinuxOS they aren't. You have to remove the configuration files manually.

[Rudge]

The problem with removing packages is that everything that was installed together with a package isn't necessarily removed with the package. So you may have to do some cleanup afterwards.

In other words:

If the package "foo" needs the package "bar" to work, you cannot uninstall "bar" without also uninstalling "foo". But the opposite is not true: you can uninstall "foo" without uninstalling "bar", even if "bar" was just installed as a dependency of "foo". This makes sense as other packages may also depend on "bar". So to get rid of everything that came with "foo" you may have to uninstall a few other packages separately.

Also note that configuration files are not always automatically uninstalled when you uninstall the package they belong to. If "foo" creates a directory .foo in your home folder, that directory will not be removed when you uninstall "foo". "Complete Removal" is often thought to mean that the configuration files are also removed, but with Synaptic in PCLinuxOS they aren't. You have to remove the configuration files manually.

Good info.