Product SiteDocumentation Site

Capítulo 5. Sistema de Pacotes: Ferramentas e Princípios Fundamentais

5.1. Estrutura de um Pacote Binário
5.2. Metainformação do Pacote
5.2.1. Descrição: O arquivo control
5.2.2. Scripts de Configuração
5.2.3. Checksums, Lista de arquivos de configuração
5.3. Estrutura de um Pacote Fonte
5.3.1. Formato
5.3.2. Uso no Debian
5.4. Manipulando Pacotes com o dpkg
5.4.1. Instalando pacotes
5.4.2. Remoção de pacote
5.4.3. Consultando o banco de dados do dpkg e inspecionando os arquivos .deb
5.4.4. Arquivo de log do dpkg
5.4.5. Suporte Multi-Arqu
5.5. Coexistencia com outros sistemas de pacotes
Como um administrador de sistemas Debian, você rotineiramente manipula pacotes .deb, já que eles contêm unidades funcionais consistentes (aplicações, documentação, etc.), cujas instalação e manutenção eles facilitam. Logo é uma boa ideia saber exatamente o que são e como usá-los.
This chapter describes the structure and contents of “binary” and “source” packages. The former are files directly usable by dpkg, while the latter contain the source code, as well as instructions for building binary packages.

5.1. Estrutura de um Pacote Binário

The Debian package format is designed so that its content may be extracted on any Unix system that has the classic commands ar, tar, and xz or sometimes gzip or bzip2. This seemingly trivial property is important for portability and disaster recovery.
Imagine, for example, that you mistakenly deleted the dpkg program, and that you could thus no longer install Debian packages. dpkg being a Debian package itself, it would seem your system would be done for... Fortunately, you know the format of a package and can therefore download the .deb file of the dpkg package and install it manually (see sidebar FERRAMENTAS dpkg, APT e ar). If by some misfortune one or more of the programs ar, tar or gzip/xz/bzip2 have disappeared, you will only need to copy the missing program from another system (since each of these operates in a completely autonomous manner, without dependencies, a simple copy will suffice). If your system suffered some even more outrageous fortune, and even these don't work (maybe the deepest system libraries are missing?), you should try the static version of busybox (provided in the busybox-static package), which is even more self-contained, and provides subcommands such as busybox ar, busybox tar and busybox xz.
In case of a misfortune you better also have a backup of your system (see Seção 9.10, “Backup”).
Dê uma olhada no conteúdo de um arquivo .deb:
$ ar t dpkg_1.19.7_amd64.deb
$ ar x dpkg_1.19.7_amd64.deb
$ ls
control.tar.gz  data.tar.xz  debian-binary  dpkg_1.19.7_amd64.deb
$ tar tJf data.tar.xz | head -n 16
$ tar tJf control.tar.xz
$ cat debian-binary
Como você pode ver, o arquivo ar de um pacote Debian é composto de três arquivos:
This is a text file which simply indicates the version of the .deb file package format version. In Debian Buster it is still version 2.0.
This archive file contains all of the available meta-information, like the name and version of the package as well as some scripts to run before, during or after (un-)installation of it. Some of the meta-information allows package management tools to determine if it is possible to install or uninstall it, for example according to the list of packages already on the machine, and if files shipped have been modified locally.
data.tar.xz, data.tar.bz2, data.tar.gz
This archive contains all of the files to be extracted from the package; this is where the executable files, libraries, documentation, etc., are all stored. Packages may use different compression formats, in which case the file will be named differently for xz, bzip2 or gzip.