Rpm delete installed packages

The methods to install and uninstall RPM package on Linux are as follows:. The installation of RMP package can be completed by using program rpm. Execute the following command. Where your-package. By default, it can not be installed correctly. In other words, RPM — I — force — nodeps can ignore all dependency and file problems, what package. Some packages end with.

Method 2. Do not type the extension on the file. For example: rpm -e gedit. Method 3. Include your email address to get a message when this question is answered. Rarely, you will need to force an installation. To do this, pass the --force argument to the rpm command. Helpful 0 Not Helpful 0.

Using the parameter -U update instead of -i install guarantees that you install the latest version of the RPM. Some packages will have dependencies. All this means is that you must install another package for the desired one to work. An example of this is Ogle, an open-source DVD player. On its own, Ogle can't play a DVD, but requires a few other programs to be installed, in addition to the main Ogle package.

If the rpm has dependencies and you don't care about satisfying them you can use the --nodeps option as well. RPM is a powerful software manager which can be used to build, install, query, verify, update, and uninstall individual software packages.

An RPM package consists of an archive of files, and package information such as name, version, a description and information about dependencies on other RPM packages. RPM is more than a Red Hat specific tool. Benefits of using RPM include:. In a source RPM are not only the original program source code files but scripts that allow the code to be recompiled automatically, to be installed automatically, and to be removed automatically.

There are no end-user executable files in a source RPM. Usually, only developers are interested in a source RPM. Binary RPM filenames identify the host architecture for the contents. For example, the binary RPM file:. To update your system with the latest version of a package, you will need the most recent binary RPM for it.

Each RPM package is contained in a single file. There are directories in the file structure that are non-empty. Is this the reason? But these non-empty directories were created by the RPM installation. So I would expect that they would be "owned" by RPM and removed automatically. RPM won't delete any files it doesn't know about, so if new files have been created in a directory that are not part of a package, RPM won't remove them, or the directories.

It will delete the directories if they are empty and it knows about them. It depends how the spec file was written. More care should be taken while specifying owned directories as there is different methods to process RPM erase on different distros. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more.