rpm

RPM Package Manager (referred to as RPM, full name of The RPM Package Manager) is a
widely used package manager under Linux. Originally developed by Red Hat, it is now also developed by the open source community. RPMs are usually included with Linux distributions, but there are also distributions (eg Gentoo)
that release RPMs separately as application software . The RPM package manager can only manage packages in the form of RPM, and RPM itself is a pre-installed package in the form of rpm. For end users, RPM makes software management very easy, and requires only very simple commands to complete the installation, uninstallation and upgrade of RPM packages. It is currently the most resourceful package type under GNU/Linux and the default software manager in RHEL and CentOS. RPM will first compile the software to be installed (if necessary) and package it. Through the preset database records in the packaged software, record the other software that the software must depend on when it is installed. When installing on a Linux system , RPM will first check whether other software depends on the Linux system according to the recorded data , if it is satisfied, it will be installed, if not, it will not be installed. This installation method is much more convenient than the method of directly compiling and installing from source code. Each RPM package is a compressed file containing content information, application files, icons, documentation, and administration scripts. The hypervisor uses this content to securely locate, install, and uninstall software. For example, the CentOS installation process uses the packages shipped with CentOS to build or upgrade symbols














system that suits your needs.
Each package file has a long name and contains several of the most important pieces of information. For example, this
is the full name of the tsclient package in CentOS:
tsclient-0.132-6.i386.rpm
Management tools typically use one of three formats when processing packages:
 Package name: tsclient
 With the version number and Distribution package name: tsclient-0.132-6
 Package name with hardware architecture: tsclient.i386
For clarity, rpm lists packages in the format "name.architecture". Repositories also typically
store packages in schema-separated directories. Every time you specify an architecture for a software package, you are actually specifying
the minimum required machine architecture for the software.

Architecture	Applicable machines
i386	Fits any existing Intel compatible computer
noarch	Suitable for all architectures
ppc	Compatible with PowerPC systems such as Apple Power Macintosh
x86_64	Compatible with 64-bit Intel processors such as Intel Core i7

Some software is optimized for special types of Intel processors,
with different packages for i386, i586, i686 and x86_64 computers. If the machine has an Intel Pentium, VIA C3 or other
compatible processor, then the i586 package can be used. If your machine has a more powerful Intel or
AMD processor, you can use the i686 package.

Notice

 There are two types of rpm packages: binary installation package (Binary) and source code installation package (Source). Binary packages can be installed directly on the computer, while source code packages will be automatically compiled and installed by RPM. Binary packages are often suffixed with rpm, and source code packages are often src.rpm

In our task, it seems very convenient to use RPM to manage software. In fact, RPM has a disadvantage that has been criticized by users for a
long time , that is, it cannot solve the problem of software dependencies. This problem is
not .
Simply put, when using RPM to install software
, package A, RPM may prompt to install package B first (A depends on package B), and package B
may depend on Software package C, software package C may depend on software package D... Some software packages depend on hundreds
of other software packages, which is very troublesome to install.
The reason is that the RPM program is already packaged data, that is to say, the
data it has been compiled, and all installations must be installed in the original host environment.
The installation environment in which the software was originally created must also be reproduced on the current host.

as a suffix.  The installation methods of rpm binary installation package and source code installation package are different.  The source code installation package is not mentioned in this task.

 

Order

Usage: rpm [options][installation package name][package name] A tool combination for automatically installing, configuring, uninstalling and upgrading software packages in RHEL and CentOS  -i <installation package file name> Install software  -v Display installation details Information (use with i)  -h output (#) as progress bar during installation (use with iv)  -e <package name> Uninstall software  --replacepkg Force install regardless of whether the package is already installed  - -test install test, do not actually install  --nodeps ignore package dependencies and force installation  --force ignore package and file conflicts package (used with q)  -p <installation package filename> List installed package names (used with q)