1 / 12

Section-2

Section-2. Installing Software's. What is RPM. Red Hat Package Manager (RPM) allows the easy installation and removal of software packages—typically, precompiled software. A package consists of an archive of files and other metadata.

tuwa
Download Presentation

Section-2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Section-2 Installing Software's

  2. What is RPM • Red Hat Package Manager (RPM) allows the easy installation and removal of software packages—typically, precompiled software. A package consists of an archive of files and other metadata. • Several Linux distributions and various third parties use this tool to distribute and package their software.

  3. RPM • An RPM file is a package that contains files needed for the software to function correctly. These files can be configuration files, binaries, and even pre- and postscripts to run while installing the software. • Maintains a central database of what RPMs you have installed, where they are installed, when they were installed, and other information about the package.

  4. Query Package • Display information about package.

  5. Verify Package • Another powerful feature is the ability to verify packages. If you are worried that you deleted an important file for some package, just verify it. You will be notified of any anomalies.

  6. RPM's Package Labels • Every package built for RPM has to have a specific set of information that uniquely identifies it. We call this information a package label. • nls-1.0-1 • perl-5.001m-4

  7. Package Components • Component #1: The Software's Name • Every package label begins with the name of the software. The name may be derived from the name of the application packaged. • it may be a name describing a group of related programs bundled together by the package builder. • nls-1.0-1 • perl-5.001m-4

  8. Component #2: The Software's Version • Next in the package label is an identifier that describes the version of the software being packaged. • nls-1.0-1 • perl-5.001m-4

  9. Component #3: The Package's Release • It is a number chosen by the package builder. It reflects the number of times the package has been rebuilt using the same version software. • The rebuilds are due to bugs uncovered after the package has been in use for a while. • nls-1.0-1 • perl-5.001m-4

  10. rpm -i — What does it do? • Performing dependency checks. • Checking for conflicts. • Performing any tasks required before the install. • Deciding what to do with config files. • Unpacking files from the package and putting them in the proper place. • Performing any tasks required after the install. • Keeping track of what it did.

  11. rpm -e — What Does it Do? • It checks the RPM database to make sure that no other packages depend on the package being erased. • It executes a pre-uninstall script (if one exists). • It checks to see if any of the package's config files have been modified. If so, it saves copies of them. • It reviews the RPM database to find every file listed as being part of the package, and if they do not belong to another package, deletes them. • It executes a post-uninstall script (if one exists). • It removes all traces of the package (and the files belonging to it) from the RPM database.

More Related