Raspberry Pi_Eng_17.1.5 Naming Rules for Package


Published Book on Amazon


All of IOT Starting with the Latest Raspberry Pi from Beginner to Advanced – Volume 1
All of IOT Starting with the Latest Raspberry Pi from Beginner to Advanced – Volume 2

출판된 한글판 도서


최신 라즈베리파이(Raspberry Pi)로 시작하는 사물인터넷(IOT)의 모든 것 – 초보에서 고급까지 (상)
최신 라즈베리파이(Raspberry Pi)로 시작하는 사물인터넷(IOT)의 모든 것 – 초보에서 고급까지 (하)

Original Book Contents


17.1.5  Naming Rules for Package

 

The package usually has a filename in the form of a "deb" extension. "deb" is an extension to the Debian software package format, which is used for binary packages. The basic format of package file name is as follows.

 

<File name>_<Version number>-< Revision number>_<Architecture name>.deb

 

   <File name> is the name of the file. This contains the name to indicate the characteristics of package, such as gimp, passwd, lpr, elm, pine, smail, sendmail. File name consists of usually alphabetic characters, numeric characters and '-' or '+' symbolic characters. Usually, the name given by the author in program unit is used. If the program is divided into several packages, the name that can indicate the corresponding contents is given.

 

   <Version number> is the version number. It will follow the version number generated by the distributor of the program. You can see that version numbers such as "2.0.29", "2.0.30" for the kernel and version numbers such as "2.7.2.1", "2.7.2.3" for the GNU C compiler. The version number is usually preceded by a number, an alphabetic character can be added according to the patch of the source, and Dot ('.') is allowed. However, there is no standard because it depends on how the author assigns the version number.

 

   <Revision number> is the revision number for the package version. Revision is a change that may happen to the package without changing the original source version due to package security problems, changes in Shell scripts, changes in package dependencies, or new compilation of sources. Starting from 1, it is usually assigned to an integer. Sometimes a decimal point is included, but it is standard to assign it to an integer.

 

   <Architecture name> specifies the platform generating binary file. When it is normally distributed, as it is stored in a directory such as "binary-{i386, powerpc, sparc, alpha, m68k}", the architecture name is omitted, but when you generate the package, it is specified explicitly. If "i386, powerpc, sparc, alpha, m68k" are valid names, and a package is platform independent (docs, cell scripts, perl scripts, etc.), "all" is specified as generation platforms.

 

Here are some examples:

    libc5_5.4.33-7_I386.deb

This package is the package named "libc5", with a version number of "5.4.3.3", a Debian revision number of "7", and the architecture in which this package can be used is a processor of "i386" family

 

    manapages_1.17-3_all.deb

This package is a package named "manapages", with a version number of "1.17", a Debian revision number of "3", and as it is a platform-independent package that is independent of the running processor, it is the package that can be installed on any platform commonly.

 

    rar-2.00-3beta.i386.rpm

This package is a Red Hat package, the package name is "rar", the version number is "2.00", and the revision number is "3beta". And the architecture in which this package can be used is "i386".