How to view the installation path of the rpm installation package

How to view the installation path rpm-qplxxxxxx.rpm1 for the rpm installation package. how to install the rpm package rmp package can be done using the program rpm. Execute the following command rpm-iyour-package.rpm where the your-package.rpm is the file name of the rpm package you want to install, usually set... how to view the installation path of the rpm installation package: rpm-qpl xxxxxx. rpm 1. you can use the program rpm to install the rpm package rmp. Run the following command rpm-I your-package.rpm where the your-package.rpm is the file name of the rpm package you want to install, typically placed under the current directory. The following warning or prompt may appear during installation :... conflict... some files may overwrite existing files in the package to be installed, in this case, the installation cannot be correctly performed using www.2cto.com rpm -- force-I to force the installation... is needed ...... is not installed... you can use rpm -- nodeps-I to ignore the required software. that is to say, rpm-I -- force -- nodeps can ignore all dependencies and file problems, any package can be installed, but this forced installation package cannot make full use of the function 2. how to install. src. rpm software package some software packages are. src. this type of software package is an rpm package that contains the source code and needs to be compiled during installation. There are two installation methods for such software packages: www.2cto.com (1 ). run rpm-I your-package.src.rpm (2 ). cd/usr/src/redhat/SPECS (3 ). rpmbuild-bp your-package.specs a specs file with the same name as your package (4 ). cd/usr/src/redhat/BUILD/your-package/a directory with the same name as your package (5 ).. /configure is the same as compiling common source code software. you can add the parameter (6 ). make (7 ). make install Method 2: (1 ). run rpm-I you-package.src.rpm (2 ). the first two steps of cd/usr/src/redhat/SPECS are the same as those of Method 1 (3 ). rpmbuild-bb your-package.specs one and your package In this case, the specs file with the same name is located in the directory/usr/src/redhat/RPM/i386/(depending on the specific package, it may be i686, noarch, etc, there is a new rpm Package, which is a compiled binary file. Run the rpm-I new-package.rpm to complete the installation. 3. how to uninstall the rpm package using the command rpm-e package name. The package name can contain the version number and other information, but cannot have a suffix. rpm-e proftpd-1.2.8- 1 rpm-e proftpd-1.2. 8 rpm-e proftpd-rpm-e proftpd may not be in the following format: rpm-e proftpd-1.2.8-1.i386.rpm rpm-e proftpd-1.2.8-1. I 386 rpm-e proftpd-1. 2 rpm-e proftpd-1 sometimes has some errors or warnings :... is needed... this indicates that this software is required by other software and cannot be detached at will. you can use rpm-e -- nodeps to forcibly uninstall it. 4. how to get the files in the rpm package without installing rpm2cpio and cpio rpm2cpio xxx. Rpm | cpio-vi rpm2cpio xxx. rpm | cpio-idmv rpm2cpio xxx. rpm | cpio -- extract -- make-directories parameter I is the same as extract, which indicates extracting files. V indicates that the execution process d is the same as make-directory, and the directory m is created based on the original path of the file in the package, which indicates that the file update time is maintained. 5. how to View rpm Package-related files and other information all the examples below assume that the software package mysql-3.23.54a-11 is used. the rpm-qa packages installed in my system list all installed packages. if you want to find all installed packages that contain a string of SQL, rpm-qa | grep SQL <2 >. how to obtain the full name of a software package file rpm-q mysql can obtain the full name of the mysql software package installed in the system, and obtain the version of the current software package. In this example, we can get the information mysql-3.23.54a-11 <3>. is the file in an rpm Package installed there? Rpm-ql package name note here is the name of the package that does not include the. rpm suffix that means you can only use mysql or mysql-3.23.54a-11 instead of mysql-3.23.54a-11.rpm. If you only want to know where the executable program is put, you can also use which, such as which mysql <4>. an rpm package contains files that have not been installed. use rpm-qlp ****. rpm is a software package that has been installed. you can also use rpm-ql ****. rpm <5>. how can I obtain the version, purpose, and other information about a software package? For a software package that has not been installed, use rpm-qip ****. rpm is a software package that has been installed. you can also use rpm-qi ****. rpm 6. which software package is installed for a program, or which package contains this program rpm-qf'which program name' returns the package's full name rpm-qif 'which program name' returns information about the package rpm-qlf 'which program name' note, it is not a quotation mark, but a key in the upper left corner of the keyboard. You can also use rpm-qilf to output the package information and file list at the same time. which software package is installed for a file, or which software package contains this file. Note that the method in the previous question only applies to executable programs. the following method, it can be used not only for executable programs, but also for common files. The premise is that you know the file name. First, obtain the complete path of the program. you can use whereis or which, and then use rpm-qf for example: # whereis ftptop: /usr/bin/ftptop/usr/share/man/man1/ftptop.1.gz # rpm-qf/usr/bin/ftptop proftpd-1.2.8-1 # rpm-qf/usr/share/doc/proftpd-1.2.8/ rfc/rfc0959.txt proftpd-1.2.8-1 summary: to obtain information about the software package, use rpm-q and q to query the query. you can use other options, such as I to represent info, to obtain the information about the software package. use l to represent list and obtain the file list; a indicates all, and queries are executed in all packages; f indicates file, and related queries are performed based on files; p indicates package. grep can be used to generate the query conditions required for queries based on software packages, or from" The command line in ''generates some knowledge about the rpm software package. 1. what is rpm, that is, RedHat Package Management, is one of the RedHat inventions 2. why is rpm required in an operating system? install software packages that implement various functions. These software packages generally have their own programs, but they also have intricate dependencies. It also needs to solve the software package version, installation, configuration, and uninstall automation problems. To solve these problems, RedHat puts forward a good way for its own system to manage thousands of software. This is the RPM Management system. After the rpm management system is installed in the system, as long as it is a package that meets the rpm file standards, you can easily install, upgrade, and uninstall 3. is it true that all linux systems use rpm and require a package management system? Therefore, many linux systems use rpm. However, the rpm system is dedicated to RH, but all systems such as TL and Mandrake also use rpm. Since the rpm source program can be compiled on other systems, it is possible to use rpm on other systems. in addition to rpm, some other systems also have their own software package management programs, for example, deb package in debian, slakware also has its own package management system 4. why is the rpm package file name so long? the rpm package file name contains the version information, operating system information, hardware requirements, and so on. For example, in the mypackage-1.1-2TL.i386.rpm, mypackage is the name of the software package registered in the system 1.1 is the software version number, 2 is the release number, TL represents for the TL operating system, or it may be RH and so on. I386 indicates that it is used on intel x86 platform, or it may be a type. 5. the i386 and i686 in the package file name contain not only the software name and version information, but also the information about the applicable hardware architecture. I386 indicates the software package is applicable to computers with x86 architectures of intel 80386 or above (AI32) i686 indicates the software package is applicable to computers with x86 architectures of intel 80686 or above (Pentium pro or above) (IA32) noarch indicates that this software package is not related to the hardware architecture and can be used in general. The program of the i686 software package is generally optimized for the CPU, so backward compatibility is used for comparison. the i386 package can be used on x86 machines. Forward is generally incompatible. However, the CPU below the Pentium pro is rarely used on current computers. Generally, the configured machines can use the i686 software package. 6. Can the rpm packages released by different operating systems be mixed? For rpm packages that have been compiled into binary files, they cannot be mixed due to different operating systems. Software packages released with src. rpm can be installed on different systems because local compilation is required during installation. 7. some special problems encountered when using rpm q I use rpm-e **. rpm cannot delete rpm Package A. the package name does not include rpm or rpm-e. It can contain version numbers and other information, but cannot have A suffix. rpm Q: Are there tools for reading RPM files in MS systems? A wincmd with rpm plugins... Q Can I install and upgrade the rpm package through ftp? A can. Rpm-ivh ftp://xxxxxxxx/PATH2SomeRPM Q What if the version of the existing package is too high during rpm installation? A sometimes because the installed software package is too old and the related software package version in the system is relatively new, some files on which the package to be installed may not be found. There are two solutions. The first is to find a file with the same or similar functions as the desired file in the system file and link it with a symbol to the desired directory. I know how to specify the installation path when installing the rpm Package in Linux, many of which are learned from the Internet. Please kindly advise. The following options are the methods you want to complete. -- prefix This sets the installation prefix For relocatable packages. -- relocate = For relocatable packages, translates the files that wocould be put in To . -- Badreloc To be used in conjunction with -- relocate, this forces the relocation even if the package isn' t relocatable. -- noorder Don't reorder the packages for an install. the list of packages wocould normally be reordered to satisfy dependences es. RPM Command Manual 1. Installation Command format: rpm-I (or -- install) options file1.rpm... fileN. rpm parameter: file1.rpm... fileN. detailed file name option of the rpm package to be installed by RPM:-h (or -- hash) output hash mark ('' # '') -- Test only tests the installation and does not actually install it. -- Percent: The installation progress is displayed as a percentage. -- Excludedocs does not install the document file in the software package -- includedocs installation documentation -- replacepkgs force reinstall installed software package -- replacefiles replace files belonging to other software packages -- force ignores conflicts between software packages and files -- noscripts does not run the pre-installation and post-installation script -- prefix to install the software package to the specified path -- ignorearch does not verify the structure of the software package -- ignoreos does not check the operating system of the software package running -- nodeps does not check the dependency relationship -- ftpproxy is used as the FTP proxy -- ftpport specifies the FTP port number as the general option-v displays additional information-vv displays debugging information-root asks RPM to use the specified path as the "root directory ", in this way, both the pre-installation program and the post-installation program will be installed in this directory -- rcfile set the rpmrc file to -- dbpath and set the path where the RPM data inventory is located. Path 2: Delete command format: rpm-e (or -- erase) options pkg1... pkgN parameter pkg1... pkgN: detailed options of the software package to be deleted -- test only executes the delete test -- noscripts does not run the pre-installation and post-installation script programs -- nodeps does not check the dependency general options-vv displays debugging information -- root allows RPM use the specified path as the "root directory ", in this way, both the pre-installation program and the post-installation program will be installed in this directory -- rcfile set rpmrc file to -- dbpath set the path of the RPM data inventory to III. upgrade command format rpm-U (or -- upgrade) options file1.rpm... fileN. rpm parameter file1.rpm... fileN. rpm software package name details option-h (or -- hash) output hash mark (''#'') -- o Ldpackage allows "upgrade" to an old version -- test only performs the upgrade test -- excludedocs does not install the document file in the software package -- includedocs installation documentation -- replacepkgs force reinstall installed software package -- replacefiles replace is files of other software packages -- force ignores conflicts between software packages and files -- percent outputs the installation progress as a percentage. -- Noscripts does not run the pre-installation and post-installation scripts -- prefix installs the software package to the specified path -- ignorearch does not verify the structure of the software package -- ignoreos does not check the operating system of the software package -- nodeps does not check the dependency -- ftpproxy is used as the FTP proxy -- ftpport specifies the FTP port number as the general option-v displays additional information-vv displays debugging information-root asks RPM to use the specified path as the "root directory "", in this way, both the pre-installation program and the post-installation program will be installed in this directory -- rcfile set rpmrc file to -- dbpath set the path of the RPM data inventory to 4. query command format: rpm-q (or -- query) options parameter: pkg1... pkgN: query the installed software package details option-p (or ''-'') query the file of the software package-f query which software package belongs-a query all installed software packages -- whatprovides query the software package that provides functionality-g query the software package that belongs to the group -- whatrequires query all required software packages information Option show all the packages logo-I show Package Overview-l show package file list-c show configuration file list-d show document file list-s show package file list and displays the status of each file-scripts displays the installation, uninstallation, validation script-queryformat (or -- qf) display query information in the way specified by the user -- dump display all verified information for each file -- provides display functions provided by the software package -- requires (or-R) show the functions required by the software package general options-v show Additional Information-vv show debugging information-root ask RPM to use the specified path as the "root directory ", in this way, both the pre-installation program and the post-installation program will be installed in this directory -- rcfile set rpmrc file to -- dbpath set the path of the RPM data inventory to 5. verify the command format of the installed software package: rpm-V (or -- verify, or-y) options parameter pkg1... pkgN package name package option to be verified-p Verify against package file-f Verify the package to which the package belongs-a Verify all package-g Verify all group package details option -- noscripts not run the validation script -- nodeps does not verify the dependency -- nofiles does not verify the file attributes common options-v displays additional information-vv displays debugging information-root allows RPM to make the specified path "root directory ", in this way, both the pre-installation program and the post-installation program will be installed in this directory -- rcfile set rpmrc file to -- dbpath set the path of RPM data inventory to 6. verify the file syntax in the software package: rpm-K (or -- checksig) options file1.rpm... fileN. rpm parameter: file1.rpm... fileN. rpm package file name Checksig -- detailed options -- nopgp does not verify PGP signature general options www.2cto.com-v show Additional Information-vv show debugging information -- rcfile set rpmrc file to seven, other RPM options -- rebuilddb re-create an RPM database -- initdb creates a new RPM database -- quiet reduces the output as much as possible -- help displays the help file -- version displays the current version of RPM