Description Rpm (software)




1 description

1.1 package filename , label
1.2 library packaging
1.3 format
1.4 spec file
1.5 srpm





description

whilst rpm format same across different linux distributions, detailed conventions , guidelines may vary across them.


package filename , label

an rpm delivered in single file, in format:



<name>-<version>-<release>.<architecture>.rpm

such as:



libgnomeuimm-2.0-2.0.0-3.i386.rpm

where <name> libgnomeuimm, <version> 2.0, <release> 2.0.0-3, , <architecture> i386.


source code may distributed in rpm packages in case <architecture> part specified src in, libgnomeuimm-2.0-2.0.0-3.src.rpm


rpms noarch.rpm extension refer packages not depend on computer s architecture. these include graphics , text program use, , programs written in interpreted programming languages such python programs , shell scripts.


the rpm contents include package label, contains following pieces of information:



software name
software version (the version taken original upstream source of software)
package release (the number of times package has been rebuilt using same version of software). field used indicating specific distribution package intended appending strings mdv (formerly, mdk ) (mandriva linux), mga (mageia), fc4 (fedora core 4), rhl9 (red hat linux 9), suse100 (suse linux 10.0) etc.
architecture package built (i386, i686, x86_64, ppc, etc.)

the package label fields not need match filename.


library packaging

libraries distributed in 2 separate packages each version. 1 contains precompiled code use @ run-time, while second 1 contains related development files such headers, etc. packages have -devel appended name field. system administrator should ensure versions of binary , development packages match.


format

the format binary , consists of 4 sections:



the lead, identifies file rpm file , contains obsolete headers.
the signature, can used ensure integrity and/or authenticity.
the header, contains metadata including package name, version, architecture, file list, etc.
a file archive (the payload), in cpio format, compressed gzip. rpm2cpio tool enables retrieval of cpio file without needing install rpm package.

more recent versions of rpm can use bzip2, lzip, lzma, or xz compression.
rpm 5.0 format supports using xar archiving.



spec file

the recipe creating rpm package spec file. spec files end in .spec suffix , contain package name, version, rpm revision number, steps build, install, , clean package, , changelog. multiple packages can built single rpm spec file, if desired. rpm packages created rpm spec files using rpmbuild tool.


spec files distributed within srpm files, contain spec file packaged along source code.


srpm

a typical rpm pre-compiled software ready direct installation. corresponding source code can distributed. done in srpm, includes spec file describing software , how built. srpm allows user compile, , perhaps modify, code itself.


a software package may contain scripts architecture-independent. in such case srpm may available; still installable rpm.








Comments

Popular posts from this blog

Biography Pavel Yablochkov

Discography Three Man Army

History VMFA-121