RPM is the abbreviation of Redhat Package Manager, the meaning of the Redhat (Red Hat) Package Manager. (Redhat is a famous Linux company, website: http://www.redhat.com) For an operating system, there is no such package manager. Without the help of the package manager, the manufacturer of the operating system release will face such or such problems, users will be installed, upgraded, and unloading and publishing software packs will also be very troublesome, and system management is also prone to problems. On the contrary, there is a special package manager, software producer is easy to make and distribute its own software, and for ordinary users, the installation and maintenance of the package will become very convenient. This situation will also play a good promotion for the promotion of an operating system. RPM is rapidly promoted with the popularity of the Redhat Linux release, and the performance of the two is easy.
When the RPM pioneer is initially, the release of the Linux system did not use the package manager. Over time, RedHatmlinux developers realize the importance of developing a package manager, so that the RPP manager is developed. Although RPP is simple, there have been several important functions. If you play a simple command, you can implement the installation and uninstallation of the software. You can include the script program executed before and after the installation before and after the installation. Check the installed package at any time, the query function is also very powerful. The disadvantage of RPP is that the RPP packaging is based on special modified (for RPP) source code, so these source code is not a pure source code. For this reason, when the software package developer wants to establish a large number of different packages, it will face many technical issues. RPP does not guarantee that the current execution program is based on packaged source programs, and RPP does not support multiprocessor architecture. At the same time as RPP, there is also a PMS (ie package management system, package management system), which is another group of Linux enthusiasts. PMS uses a pure source code that allows the package producer to quickly release the latest version of the software, and can see the change in the software immediately. RPM adopts this wise practice, which is also a significant contribution to RPM in PMS. The disadvantage of PMS is that the query function is not strong, there is no package verification function, does not support multi-architecture, and database design is not good. After RPP and PMS, Rik Faith and Doug Hoffman have developed a PM manager. The manager integrates many of the functions of RPP and PMS, but database design is not strong and still does not support multi-architecture.
RPM development, Marc Ewing and Erik Troan have developed RPM software package manager with Perl based on the experience of absorbing RPP, PMS, and PM design, which is RPM1.0. The success is that the configuration file can be automatically handled; a large number of packages can be reconstructed; The deficiency is: the program is large, the run is slow, because it is written in the language of Perl; the database function is too weak; the multi-architecture is not supported; the package file format is not expandable. For the weaknesses of RPM1.0, RPM developers are again working to upgrade RPM to 2.0, 3.0 and now version 4.0. They mainly did the following: rewrite the program with C, which greatly increases the RPM running speed. The RPM database format has been re-designed, and the focus is improved in both performance and reliability. The package format has also been re-designed, which is convenient for future extension and upgrade. RPMLIB (RPM library) is established to facilitate other programs to call RPM. Increase multi-system support, facilitate the RPM cross-platform use (whether it is an X86 system or other system such as SPARC).
The online RPM RPM official website is http://www.rpm.org, the website publishes the latest news of RPM, about the instructions for RPM, you can also download the latest RPM software source code and execution code, often go to see Look.
Summary Today's RPM makes the package installation and uninstallation, check if the installed package is easy, and the program (source program or execution program) is also simple, cross-platform support, follow the GPL copyright release source code , Make RPM more widely apparent application and promotion. RPM is popular with Linux and non-Linux world. If you want to know, even the rpm, please come with me! ----------------------------------- -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- --- First, install the command format: rpm -i (or --install) Options file1.rpm ... filen.rpm parameter: file1.rpm ... filen.rpm will be installed with the RPM package file name detailed options : -H (or --hash) Outputs the Hash mark (`` # '') --Test is only tested for the installation, and is not actually installed. --Percent outputs the scheduled progress in the form of a percentage. --ExCludedocs Do not install document files in the package - Remnocs to reinstall the installed package - Replacing files belonging to other packages - AllCeFiles Replace the Conflict for other packages - AllCE ignore packages and files --Noscripts Do not run pre-installation and post-installation scripts - PREFIX Install the package to the structure of the software package on the specified path - IGNOREOS does not check the operating system that the package is running running the software package - NodePs does not check the dependency relationship --ftPPROXY is used as a port number for FTP proxy -ftPort specifies that FTP is common option -v Display additional information -VV display debugging information -root allows RPM to make the specified path as "root directory", so pre-installer and The installer will be installed into this directory - RCFile Set the RPMRC file to -dbPath Set the path to the RPM data inventory is two, delete the command format: rpm -e (or --rase) Options Pkg1 ... PKGN parameter PKG1. .. pkgn: Package Details Options To Delete - Test only Execute Deleted Test - Noscripts Does Not Run Pre-installation and Post Installed Script Programs - NodePs Does Relative General Options - VV Display Debug Information - ROOT Let RPM Make the specified path as "root directory" so that the pre-installer and the post-installer are installed in this directory - RcFile Set the RPMRC file to -dbPath Set the path to the RPM data inventory is three, upgrade command format rpm - U (or --upgrade) options file1.rpm ... filen.rpm parameter file1.rpm ... filen.rpm Detailed options - Hash marks when the (or --hash) is installed (`` # '') --OLDPACKAGE Allows "Upgrade" to an old version - Test only upgrade test --ExCludedocs Do not install document file in the package - Includedocs installation document - ReplacingPKGS Forced reinstall installed package - Replacefiles Replace files belonging to other packages - the conflict of theforce ignores the packages and files --percent outputs the scheduled progress in the percentage form.
