Product SiteDocumentation Site

Chapter 1. Exploring the Structure of Packages

1.1. Packaging with RPM
1.1.1. Why Package Software with RPM?
1.2. Package Design
1.2.1. Package File Name
1.2.2. Format of the Archived Files
1.2.3. Querying Packages
This chapter describes the package design, defines the basic content of every package, and shows how to explore the package structure.

1.1. Packaging with RPM

The Red Hat Package Manager (RPM) makes it easier for you to distribute, manage, and update software that you create for Red Hat Enterprise Linux. This chapter provides basic information on how to package your software into an RPM.

1.1.1. Why Package Software with RPM?

Many software vendors distribute their software via a conventional archive file (such as a tarball). However, there are several advantages in packaging software into an RPM. These advantages include:
  • Each RPM package includes metadata that describes the package's components, version, release, size, project URL, installation instructions, and so on.
  • Users can use a set of standard package management tools (for example yum or PackageKit) to install, remove, and manage your software.
  • With the standard package management tools, you can directly distribute your software, including any software updates, to your users.