An RPM package can contain an arbitrary set of files. Faith and Kevin Martin in the fall of 1993 for the Bogus Linux Distribution. A site often has its own RPM repositories which may either act as local mirrors of such internet repositories or be locally fedora installation steps pdf collections of useful RPMs. RPM ease the process of obtaining and installing RPMs from repositories and help in resolving their dependencies.
Multiple databases are created for indexing purposes, replicating data to speed up queries. 386, i686, x86_64, ppc, etc. The package label fields do not need to match the filename. Libraries are distributed in two separate packages for each version. One contains the precompiled code for use at run-time, while the second one contains the related development files such as headers, etc. Those packages have “-devel” appended to their name field.
The system administrator should ensure that the versions of the binary and development packages match. The lead, which identifies the file as an RPM file and contains some obsolete headers. The “Recipe” for creating an RPM package is a spec file. Spec files end in the “. RPM revision number, steps to build, install, and clean a package, and a changelog. Multiple packages can be built from a single RPM spec file, if desired. RPM packages are created from RPM spec files using the rpmbuild tool.
Spec files are usually distributed within SRPM files, which contain the spec file packaged along with the source code. A typical RPM is pre-compiled software ready for direct installation. The corresponding source code can also be distributed. This is done in an SRPM, which also includes the “SPEC” file describing the software and how it is built. The SRPM also allows the user to compile, and perhaps modify, the code itself. A software package may contain only scripts that are architecture-independent.