Inside of the “Downloads” directory, the Google Earth Pro RPM package resides. To get the RPM package installed on your Fedora Linux PC, you need only run the dnf install command below. Sudo dnf install google-earth-pro-stable-current.x8664.rpm. Once the RPM package is installed on Fedora, Google Earth Pro is ready to use! Jan 20, 2021 Removing Packages in Arch. Arch Linux gives you the control to remove packages once you don't need them, and that's one of the many reasons why you should install Arch Linux. You can remove almost any package from your system if you have the authorization, of course. Let's see how you can delete a package on Arch Linux. Remove Packages With Pacman. Sudo apt update sudo apt install mono-devel. After installing the Mono runtime tool on Ubuntu/Debian, you can also install the Mono IDE (MonoDevelop) package on your system by running the following command on the shell with root access. Sudo apt-get install monodevelop. Install Mono on Red Hat Linux Enterprise. Arch (and any based ditros on it) does not rely on RPM 1 format, that's is in fact developed and used by Red Hat derivates. There are some cases (e.g. This one 2) in which a RPM package is used to install an application on Arch (and derivates) systems, but prior to do this, the RPM is extracted and handled/converted in the Arch flavour. Fresh installation using RPM. If you are performing a fresh installation on a Linux computer that supports the Red Hat Package Manager (rpm), you can install the packages individually. For example, to install the Centrify Audit & Monitoring Service package you would enter commands similar to the following: rpm -i CentrifyDA-5.4.0-platform.arch.rpm.

Maintaining Software Using RPM (Red Hat Package Manager)

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. Many other modern distributions, such as Ubuntu and SuSE, use RPM too. Benefits of using RPM include:

Simplified software distribution, installation, upgrading and removal
Guarantees that:
- prerequisite software is installed on system.
- versions of prerequisite software stay compatible.
- locally-modified configuration files are not clobbed when the RPM is updated.
- locally-modified configuration files are saved with an “.rpmsave” suffix if the package is later deleted.
Allows certification that installed software has not been altered, modified, corrupted, or changed in any way.

RPM keeps information about installed packages under the “/var/lib/rpm” directory.

Components of the RPM tool are:

A custom database containing information about all software installed on the system, collected from the individual RPMs.
A “/bin/rpm” executable.
Internet-accessible repositories of available RPM packages.

Types of RPM Packages

RPM packages come in two categories: source and binary.

A source RPM can always be recognized because the filename ends with the string “.src.rpm“. 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.

A binary RPM contains the end-user compoments of an RPM. Binary RPM filenames identify the host architecture for the contents. For example, the binary RPM file:

It contains files only usable on a 64-bit Intel X86 architecture CPU. Other common architecture values include “i386” for 32-bit Intel hosts. Some binary RPM’s may be installed on any CPU architecture because their files will work on any host; an example of these “.noarch.rpm” packages is the “tzdata” RPM which contains information about world timezones. To update your system with the latest version of a package, you will need the most recent binary RPM for it.

RPM Naming Scheme

Each RPM package is contained in a single file. The filename has several fields to fully identify the contents of the package. While the RPM tools themselves do not rely upon the filename itself, you should understand the filename convention to help you identify or download the proper package. Here is an example RPM filename:

This RPM is for the BASH shell (“/bin/bash”). The filename is composed of several parts:

where:

[name]

version] identifies which edition of the software this RPM contains. The [version] number is assigned by the program’s author. Using the number allows one to determine which version of the author’s sources were used to generate the RPM.
[release] provides the edition number of the RPM file itself and not the version of the author’s source files. An updated RPM may be issued to supply a patched version of the author’s original software. The patch need not have come from the original developer, so the RPM [release] gets incremented instead of the [version].
[arch] describes the contents of the RPM and tells whether this file contains the product source (a “.src.rpm”), architecture-independent files (a “.noarch.rpm”), or files which may only be installed on a particular host type (a “.sh.rpm” will work only on a STRONGHOLD embedded processor).

Note: The [version] is controlled by the original author and the [release] is controlled by whomever constructed the RPM.

Understanding RPM Versions

The RPM [version] and [release] fields are not always strictly numeric and may contain other characters besides ordinary digits. It is common to see both a version “10” and a “10a” version of the same package. Sometimes picking the most recent version can be tricky. Here is how RPM itself compares version and release numbers internally:

1. Remove the [name] prefix and the “.[arch].rpm” suffix. For example,:
“bash-3.1-16.1.x86_64.rpm” becomes “3.1-16.1” and “bash-3.1-16.5a.1.x86_64.rpm” becomes “3.1-16.5a.1”

Install Rpm Package On Arch Linux Command

2. Compare the remaining strings character-by-character, left-to-right until a digit is encountered. If the characters differ, whichever character comes later in the collating sequence is the more recent RPM.

3. When a digit is encountered, convert the entire sequence of digits into a single binary number. In our example, the two characters “16” are combined into a value of sixteen (16). The resulting binary values are compared and the greater value is the more recent RPM. Thus, an RPM with a [version] of “0010” is more recent than one with a [version] of “9”.

Steps 2 and 3 are repeated as necessary until a difference occurs.

Installing and Removing Files

Note: Usually only one or of an RPM may be installed at once.

Later versions are usually installed using the “-U” (update) RPM function instead of the “-i” RPM function. Common exceptions to the only-one RPM rule are the kernel RPM’s. A system commonly has several versions of kernels installed; RPM has a list of which RPM’s may have multiple versions installed. To delete one version when several are installed, you must fully-specify the package name and version.

On the x86_64 architecture, it is common to have both the 32-bit “.i386” and the 64-bit “.x86_64” RPM packages installed tosupport both 32-bit and 64-bit applications. Normally, RPM does not display the architecture of a package on a query but you can manually display it.

Installation and Removal

Common Options
Output: -v (verbose – file name), -h (hash)
Preconditions: –nodeps, –replacefiles, –force (BE CAREFUL HERE !!!)
Relocating: –excludepath, –prefix, –relocate, –badreloc, –root
URL Support: ftp, http

Examples:

Hint: Never, ever, use the “-U” option to install a new kernel RPM. The “-U” update function first deletes the current RPM from the system and then attempts to install the new RPM. Any problem that prevents the new RPM from installing will leave the system unbootable. This is not what you want, so always use the “-i” switch to install a kernel RPM.

Queries (Packages and/or Information)

Use a query for information about installed