15.3. Creación de un repositorio de paquetes para APT
Falcot Corp gradualmente comenzó a mantener una cantidad de paquetes Debian con modificaciones locales de paquetes existentes o creados desde cero para distribuir datos y programas internos.
To make deployment easier, they want to integrate these packages in a package archive that can be directly used by APT. For obvious maintenance reasons, they wish to separate internal packages from locally-rebuilt packages. The goal is for the matching entries in a /etc/apt/sources.list.d/falcot.list
file to be as follows:
deb http://packages.falcot.com/ updates/
deb http://packages.falcot.com/ internal/
The administrators therefore configure a virtual host on their internal HTTP server, with /srv/vhosts/packages/
as the root of the associated web space. The management of the archive itself is delegated to the mini-dinstall
command (in the similarly-named package). This tool keeps an eye on an incoming/
directory (in our case, /srv/vhosts/packages/mini-dinstall/incoming/
) and waits for new packages there; when a package is uploaded, it is installed into a Debian archive at /srv/vhosts/packages/
. The mini-dinstall
command reads the *.changes
file created when the Debian package is generated. These files contain a list of all other files associated with the version of the package (*.deb
, *.dsc
, *.diff.gz
/*.debian.tar.gz
, *.orig.tar.gz
, or their equivalents with other compression tools), and these allow mini-dinstall
to know which files to install. *.changes
files also contain the name of the target distribution (often unstable
) mentioned in the latest debian/changelog
entry, and mini-dinstall
uses this information to decide where the package should be installed. This is why administrators must always change this field before building a package, and set it to internal
or updates
, depending on the target location. mini-dinstall
then generates the files required by APT, such as Packages.gz
.
La configuración de mini-dinstall
necesita definir un archivo ~/.mini-dinstall.conf
; en el caso de Falcot Corp, su contenido es el siguiente:
[DEFAULT]
archive_style = flat
archivedir = /srv/vhosts/packages
verify_sigs = 0
mail_to = admin@falcot.com
generate_release = 1
release_origin = Falcot Corp
release_codename = stable
[updates]
release_label = Recompiled Debian Packages
[internal]
release_label = Internal Packages
Una decisión importante es la generación de archivos
Release
para cada repositorio. Esto puede ayudar a gestionar las prioridades de instalación utilizando el archivo de configuración
/etc/apt/preferences
(revise el
Sección 6.2.5, “Gestión de prioridades de los paquetes” para más detalles).
Ejecutar mini-dinstall
en realidad inicia un demonio en segundo plano. Mientras ejecute el demonio, revisará el directorio incoming/
por nuevos paquetes cada media hora; cuando detecte un nuevo paquete lo moverá al repositorio y generará los archivos Packages.gz
y Sources.gz
. Si ejecutar un demonio es un problema, también puede invocar manualmente mini-dinstall
en modo de lote (con la opción -b
) cada vez que suba un paquete al directorio incoming/
. mini-dinstall
permite otras posibilidades documentadas en su página de manual mini-dinstall(1).