Product SiteDocumentation Site

5.2. Informasi-Meta Paket

The Debian package is not only an archive of files intended for installation. It is part of a larger whole and describes its relationship with other Debian packages (requisites, dependencies, conflicts, suggestions). It also provides scripts that enable the execution of commands at different stages in the package's lifecycle (installation, upgrade, removal). These data are used by the package management tools, but are not part of the packaged software; they are, within the package, what is called its “meta-information” - information about other information.

5.2.1. Penjelasan: Berkas control

Berkas ini menggunakan struktur yang mirip dengan header surel (sebagaimana didefinisikan oleh RFC 2822) dan sepenuhnya dijelaskan dalam Kebijakan Debian dan halaman manual deb-control(5) dan deb822(5).
Contohnya, untuk apt, berkas control nampak sebagai berikut:
$ apt-cache show apt
Package: apt
Version: 2.2.4
Installed-Size: 4337
Maintainer: APT Development Team <deity@lists.debian.org>
Architecture: amd64
Replaces: apt-transport-https (<< 1.5~alpha4~), apt-utils (<< 1.3~exp2~)
Provides: apt-transport-https (= 2.2.4)
Depends: adduser, gpgv | gpgv2 | gpgv1, libapt-pkg6.0 (>= 2.2.4), debian-archive-keyring, libc6 (>= 2.15), libgcc-s1 (>= 3.0), libgnutls30 (>= 3.7.0), libseccomp2 (>= 2.4.2), libstdc++6 (>= 9), libsystemd0
Recommends: ca-certificates
Suggests: apt-doc, aptitude | synaptic | wajig, dpkg-dev (>= 1.17.2), gnupg | gnupg2 | gnupg1, powermgmt-base
Breaks: apt-transport-https (<< 1.5~alpha4~), apt-utils (<< 1.3~exp2~), aptitude (<< 0.8.10)
Description-en: commandline package manager
 This package provides commandline tools for searching and
 managing as well as querying information about packages
 as a low-level access to all features of the libapt-pkg library.
 .
 These include:
  * apt-get for retrieval of packages and information about them
    from authenticated sources and for installation, upgrade and
    removal of packages together with their dependencies
  * apt-cache for querying available information about installed
    as well as installable packages
  * apt-cdrom to use removable media as a source for packages
  * apt-config as an interface to the configuration settings
  * apt-key as an interface to manage authentication keys
Description-md5: 9fb97a88cb7383934ef963352b53b4a7
Tag: admin::package-management, devel::lang:ruby, hardware::storage,
 hardware::storage:cd, implemented-in::c++, implemented-in::perl,
 implemented-in::ruby, interface::commandline, network::client,
 protocol::ftp, protocol::http, protocol::ipv6, role::program,
 scope::application, scope::utility, suite::debian, use::downloading,
 use::organizing, use::playing, use::searching, works-with-format::html,
 works-with::audio, works-with::software:package, works-with::text
Section: admin
Priority: required
Filename: pool/main/a/apt/apt_2.2.4_amd64.deb
Size: 1491328
MD5sum: 24d53e8dd75095640a167f40476c0442
SHA256: 75f07c4965ff0813f26623a1164e162538f5e94defba6961347527ed71bc4f3d
Let us have a closer look at the purpose of some of the fields listed by the previous command.

5.2.1.1. Ketergantungan: Field Depends

The dependencies are defined in the Depends field in the package header. It is a list of conditions to be met for the package to work correctly. This information is used by tools such as apt in order to install the required libraries, tools, drivers, etc., in appropriate versions fulfilling the dependencies of the package to be installed. For each dependency it is possible to restrict the range of versions that meet that condition. In other words, it is possible to express the fact that we need the package libc6 in a version equal to or greater than “2.15” (written “libc6 (>= 2.15)”). Version comparison operators are as follows:
  • <<: kurang dari;
  • <=: kurang atau sama dengan;
  • =: sama dengan (catat bahwa “2.6.1” tidak sama dengan “2.6.1-1”);
  • >=: lebih dari atau sama dengan;
  • >>: lebih dari.
In a list of conditions to be met, the comma serves as a separator. It must be interpreted as a logical “and”. In conditions, the vertical bar (“|”) expresses a logical “or” (it is an inclusive “or”, not an exclusive “either/or”). Carrying greater priority than “and”, it can be used as many times as necessary. Thus, the dependency “(A or B) and C” is written A | B, C. In contrast, the expression “A or (B and C)” should be written as “(A or B) and (A or C)”, since the Depends field does not tolerate parentheses that change the order of priorities between the logical operators “or” and “and”. It would thus be written A | B, A | C.
The dependencies system is a good mechanism for guaranteeing the operation of a program, but it has another use with “meta-packages”. These are empty packages that only describe dependencies. They facilitate the installation of a consistent group of programs pre-selected by the meta-package maintainer; as such, apt install meta-package will automatically install all of these programs using the meta-package's dependencies. The gnome, kde-full and linux-image-amd64 packages are examples of meta-packages.

5.2.1.2. Konflik: field Konflik

Field Konflik menandakan ketika paket tidak dapat diinstall secara simultan dengan paket lain. Alasan yang paling umum untuk hal ini ialah kedua paket menyertakan berkas dengan nama dan path yang sama, atau menyediakan layanan yang sama pada port TCP yang sama, atau akan menghalangi operasi satu sama lain.
dpkg akan menolak memasang paket jika menimbulkan konflik dengan paket yang telah terpasang, kecuali paket yang baru menetapkan akan "menggantikan" paket terpasang, yang dalam kasus tersebut dpkg akan memilih untuk mengganti paket lama dengan yang baru. apt selalu mengikuti instruksi Anda: jika Anda memilih untuk memasang paket baru, akan secara otomatis menawarkan untuk membongkar paket yang menimbulkan masalah.

5.2.1.3. Ketidakcocokan: Field Break

Field Break (rusak) memiliki efek yang mirip dengan field Konflik, namun memiliki makna khusus. Ini menandakan bahwa instalasi paket akan “merusak” paket lain (atau beberapa versinya). Secara umum, ketidakcocokan antara kedua paket ini bersifat fana, dan hubungan Break secara khusus mengacu pada ketidakcocokan versi.
dpkg akan menolak memasang paket yang merusak paket terpasang, dan apt akan mencoba menyelesaikan masalahnya dengan memutakhirkan paket yang akan rusak dengan versi yang lebih baru (yang diasumsikan diperbaiki dan, sehingga, cocok kembali).
Situasi semacam ini mungkin terjadi ketika pembaruan tanpa kompabilitas ke belakang: hal ini terjadi jika versi baru tidak lagi dapat berfungsi dengan versi lama, dan menimbulkan tidak berfungsi di program lain tanpa membuat ketentuan khusus. Field Breaks menghalangi pengguna untuk masuk ke masalah ini.

5.2.1.4. Item Disediakan: Field Provides

Field ini memerkenalkan konsep yang sangat menarik dari sebuah “paket virtual”. Memiliki banyak aturan, namun dua yang terkadang penting. Aturan pertama berupa penggunaan paket virtual menghubungkan layanan umum dengannya (paket “menyediakan” layanan). Kedua menandakan bahwa paket menggantikan yang lainnya, dan dengan tujuan ini dapat juga memenuhi ketergantungan yang dipenuhi lainnya. Memungkinkan untuk membuat pengganti paket tanpa menggunakan nama paket yang sama.
5.2.1.4.1. Menyediakan sebuah “Layanan”
Mari membahas kasus pertama secara lebih mendetail dengan sebuah contoh: seluruh server mail, seperti postfix atau sendmail dikatakan “menyediakan” paket virtual mail-transport-agent. Nah, beberapa paket memerlukan layanan ini agar berfungsi (mis. manajer mailing list, seperti smartlist atau sympa) hanya perlu menyatakan ketergantungannya memerlukan mail-transport-agent daripada menentukan daftar banyak solusi yang memungkinkan namun tak lengkap (mis. postfix | sendmail | exim4 | …). Lebih jauh, sangat tidak berguna untuk memasang dua server mail di mesin yang sama, itulah mengapa setiap paket ini menjelaskan konflik dengan paket virtual mail-transport-agent. Konflik antara suatu paket dan dirinya sendiri diabaikan oleh sistem, namun teknik ini akan menghalangi instalasi dua server mail berdampingan.
5.2.1.4.2. Ketergantian dengan Paket Lain
The Provides field is also interesting when the content of a package is included in a larger package. For example, the libdigest-md5-perl Perl module was an optional module in Perl 5.6, and has been integrated as standard in Perl 5.8 (and later versions, such as 5.32.1 present in Bullseye). As such, the package perl has since version 5.8 declared Provides: libdigest-md5-perl so that the dependencies on this package are met if the user has Perl 5.8 (or newer). The libdigest-md5-perl package itself has eventually been deleted, since it no longer had any purpose when old Perl versions were removed.
Penggunaan field Provides untuk mengabaikan ketergantungan

Gambar 5.1. Penggunaan field Provides untuk mengabaikan ketergantungan

Fitur ini sangat berguna, karena tak mungkin untuk mengantisipasi lika-liku pengembangan, dan perlu untuk mengatur penamaan, dan penggantian otomatis lainnya, dari perangkat lunak yang usang.
5.2.1.4.3. Batasan Masa Lalu
Virtual packages used to suffer from some limitations, the most significant of which was the absence of a version number. To return to the previous example, a dependency such as Depends: libdigest-md5-perl (>= 1.6), despite the presence of Perl 5.10, would have never been considered as satisfied by the packaging system — while in fact it most likely was satisfied. Unaware of this, the package system chose the least risky option, assuming that the versions do not match.
This limitation has been lifted in dpkg 1.17.11, and is no longer relevant. Packages, like perl 5.32.1, can assign a version to the virtual packages they provide, such as Provides: libdigest-md5-perl (= 2.55.01), and thus allow other packages to use versioned dependencies.

5.2.1.5. Mengganti Berkas: Field Replaces

The Replaces field indicates that the package contains files that are also present in another package, but that the package is legitimately entitled to replace them. Without this specification, dpkg fails to install the package, stating that it cannot overwrite the files of another package (technically, it is possible to force it to do so with the --force-overwrite option, but that is not considered standard operation). This allows identification of potential problems and requires the maintainer to study the matter prior to choosing whether to add such a field.
Penggunaan field ini adil ketika nama paket berganti atau ketika paket di sertakan pada paket lainnya. Hal ini juga terjadi ketika maintainer memutuskan untuk mendistribusikan berkas dengan cara yang berbeda antara berbagai paket biner yang dibuat dari paket sumber yang sama: pengganti berkas tidak lagi dimiliki paket lama, namun hanya yang baru.
Jika seluruh berkas pada paket terinstall telah diganti, paket tersebut dianggap perlu untuk dihapus. Akhirnya, field ini juga mendorong dpkg untuk menghapus paket yang diganti ketika ada konflik.

5.2.2. Skrip Konfigurasi

In addition to the control file, the control.tar.gz archive for each Debian package may contain a number of scripts, called by dpkg at different stages in the processing of a package. The Debian Policy describes the possible cases in detail, specifying the scripts called and the arguments that they receive. These sequences may be complicated, since if one of the scripts fails, dpkg will try to return to a satisfactory state by canceling the installation or removal in progress (insofar as it is possible).
Umumnya, skrip preinst dieksekusi sebelum instalasi paket, sedangkan postinst mengikutinya. Begitu pula, prerm dipanggil sebelum penghapusan sebuah paket dan postrm setelahnya. Pembaruan sebuah paket sama dengan penghapusan versi sebelumnya dan instalasi yang baru. Tidak memungkinkan untuk menjelaskan secara mendetail seluruh kemungkinan skenario di sini, namun kita akan membahas dua yang paling umum: instalasi/pembaruan dan penghapusan.

5.2.2.1. Instalasi dan Pembaharuan

During the initial installation and for each upgrade of a package, dpkg calls the so called maintainer scripts such as the prerm or preinst scripts. These scripts can perform additional actions during the different stages of a package's life-cycle. Script names preceded by new- are the scripts from the new version of a package being installed or upgraded to. Script names preceded by old- are the scripts from the old version of a package that is being upgraded from.
During each invocation dpkg will pass certain arguments to each script such as upgrade new-version. The invoked script can then either handle the arguments and perform a particular action, or ignore the arguments and return with an exit code of 0, if nothing needs to be done during that step. In practice many packages will not need to perform an action during every step in the life cycle. Thus a typical configuration script will check for a particular argument and ignore all other ones, implicitly returning with exit code 0.
Here is what happens during an installation (or an update). The old-version, new-version and last-version-configured arguments are placeholders for the actual (old and new) version numbers of the package:
  1. For an update, dpkg calls the old-prerm script and passes upgrade new-version as arguments.
  2. Still for an update, dpkg then executes the new-preinst script with the arguments upgrade old-version; for the initial installation, it executes the new-preinst script and passes install as argument. It may add the old version in the last parameter, if the package has already been installed and removed since (but not purged, and thus configuration files have been retained).
  3. Berkas-berkas paket baru kemudian dibongkar. Jika berkas telah ada, diganti, namun salinan backup dibuat untuk sementara.
  4. For an update, dpkg executes the old-postrm script and passes upgrade new-version as arguments.
  5. dpkg memerbarui semua data internal (daftar berkas, skrip konfigurasi, dll.) dan membuang backup berkas yang tergantikan. Inilah maksud dari tidak ada kembali: dpkg tidak lagi dapat mengakses elemen yang diperlukan untuk kembali ke kondisi sebelumnya.
  6. dpkg akan memerbarui berkas konfigurasi, menanyakan pengguna untuk memutuskan jika tidak dapat secara otomatis mengatur tugas ini. Prosedur ini dibahas secara mendetail di Bagian 5.2.3, “Checksums, List of Configuration Files, et al.”.
  7. Finally, dpkg configures the package by executing the new-postinst script with the arguments configure last-version-configured.

5.2.2.2. Penghapusan Paket

The steps to remove a package are analogous to the installation steps. The main difference is that the removal scripts of the package are called:
  1. dpkg calls the prerm script and passes the remove argument.
  2. dpkg removes all of the package's files, with the exception of the configuration files and maintainer scripts.
  3. dpkg executes the postrm script and passes remove as argument. Afterwards, all of the maintainer scripts, except the postrm script, are removed. If the user has not used the “purge” option, the process stops here.
  4. For a complete purge of the package (command issued with dpkg --purge or dpkg -P), the configuration files are also deleted, as well as a certain number of copies (*.dpkg-tmp, *.dpkg-old, *.dpkg-new) and temporary files; dpkg then executes the postrm script and passes purge as argument.
Empat skrip yang dijelaskan di atas dilengkapi oleh skrip config, disediakan oleh paket menggunakan debconf untuk mendapatkan informasi dari pengguna untuk konfigurasi. Selama instalasi, skrip ini menentukan secara mendetail pertanyaan yang diminta oleh debconf. Responnya direkaom dalam basisdata debconf untuk preferensi mendatang. Skrip umumnya dieksekusi oleh apt sebelum instalasi paket satu demi satu agar mengelompokkan pertanyaan dan memintanya semua ke pengguna pada awal proses. Skrip instalasi pre- dan post- kemudian dapat menggunakan informasi ini untuk beroperasi berdasarkan keinginan pengguna.

5.2.3. Checksums, List of Configuration Files, et al.

In addition to the maintainer scripts and control data already mentioned in the previous sections, the control.tar.gz archive of a Debian package may contain other interesting files.
The first, md5sums, contains the MD5 checksums for all of the package's files. Its main advantage is that it allows dpkg --verify (which we will study in Bagian 14.3.4.1, “Mengaudit Paket-paket dengan dpkg --verify) and debsums (from the package of the same name; see Bagian 14.3.4.2, “Mengaudit Paket: debsums dan keterbatasannya”) to check if these files have been modified since their installation. Note that when this file doesn't exist, which might be the case for some older packages, dpkg will generate it dynamically at installation time (and store it in the dpkg database just like other control files).
The file conffiles lists package files that must be handled as configuration files (see also deb-conffiles(5)). Configuration files can be modified by the administrator, and dpkg will try to preserve those changes during a package update.
Efeknya, dalam situasi ini, dpkg bertindak secerdas mungkin: jika berkas konfigurasi standar tidak berubah antara kedua versi, tidak dilakukan apapu. Akan tetapi, jika berkas telah berubah, akan mencoba untuk memebarui berkas ini. Duah kasus yang mungkin: antara administrator tidak menyentuh berkas konfigurasi ini, dalam hal ini dpkg menginstall versi baru secara otomatis; atau berkas telah dimodifikasi, dalam hal ini dpkg meminta administrator versi mana yang ingin digunakan (versi lama yang dimodifikasi, atau yang baru yang disediakan oleh paket). Untuk membantu memutuskan, dpkg menawarkan untuk menampilkan sebuah “diff” yang menunjukkan perbedaan antara dua versi. Jika pengguna memilin untuk memertahankan versi lama, yang baru akan disimpan di lokasi yang sama dalam berkas dengan akhiran .dpkg-dist. Jika pengguna memilih versi baru, yang lama akan dipertahankan dalam sebuah berkas dengan akhiran .dpkg-old. Yang lainnya aksi yang tesedia berisi mengganggu sesaat dpkg untuk menyunting berkas dan berusaha mengatur kembali modifikasi yang sesuai (sebelumnya teridentifikasi oleh diff).
The control archive frequently contains other files as well, like triggers, shlibs, or symbols. These files are well described in deb-triggers(5), deb-shlibs(5), and deb-symbols(5).
Triggers were introduced to reduce the amount of duplicated events during package installation, such as file registration or catalog/database update tasks. Packages can define their own or activate defined triggers. A more comprehensive documentation can be found in /usr/share/doc/dpkg/triggers.txt.gz.
The shlibs system is an older and simpler alternative to the symbols system for declaring dependencies for shared libraries. It defines the package name and version in which to find a specific SONAME-version of a shared library. The newer symbols system allows to define the dependency by tracking the symbols and when they have been introduced or changed in the library instead.