srch

Reported by: Wouter Verhelst <wouter@debian.org> Date: Mon, 20 Sep 2021 16:57:02 UTC. Severity: minor. Found in version openstack-meta-packages/0.31. Fixed in version openstack-meta-packages/0.32

Description

These files are executable scripts which are automatically run before or after a package is installed. Along with a file named control , all of these files are ...

1 Package

This file contains various values which dpkg , dselect, apt-get , apt-cache, aptitude, and other package management tools will use to manage the package. It is defined by the Debian Policy Manual, 5 "Control files and their fields" . Here is the control file dh_make created for us:

Each Debian package contains the master 'control' file, which contains a number of fields, or comments when the line starts with '#'.

The DEBIAN/control file contains the most vital (and version-dependent) information about a binary package. It consists of a single paragraph. The fields in this file are: Package (mandatory) Source Version (mandatory) Section (recommended) Priority (recommended) Architecture (mandatory) Essential Depends et al Installed-Size Maintainer (mandatory)

Each Debian binary package contains the master control file, which contains a number of fields. Each field begins with a tag, such as Package or Version (case insensitive), followed by a colon, and the body of the field. Fields are delimited only by field tags.

The debian/control file contains the most vital (and version-independent) information about the source package and about the binary packages it creates. The first paragraph of the control file contains information about the source package in general. The subsequent paragraphs each describe a binary package that the source tree builds.

control Description Each Debian package contains the master 'control' file, which contains a number of fields, or comments when the line starts with '#'. Each field begins with a tag, such as Package or Version (case insensitive), followed by a colon, and the body of the field. Fields are delimited only by field tags.

The debian/control file contains the most vital (and version-independent) information about the source package and about the binary packages it creates. The ...

Comprehensive Debian control file example Raw control This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn ...

The debian/control file contains the most vital (and version-independent) information about the source package and about the binary packages it creates.

Except for Enhances and Breaks, they appear in the depending (binary) package’s control file. ( Enhances appears in the recommending package’s control file, and Breaks appears in the version of depended-on package which causes the named package to break). A Depends field takes effect only when a package is to be configured.

4.1. Packaging tarball. Here is an example of creating a simple Debian package from a simple C source using the Makefile as its build system. Let’s assume this upstream tarball to be debhello-0.0.tar.gz. This type of source is meant to be installed as a non-system file as: $ tar -xzmf debhello-0.0.tar.gz $ cd debhello-0.0 $ make $ make install.

The Debian binary package is a special archive file which holds a set of installable binary data with its associated information. A single Debian source package may generate multiple Debian binary packages defined in the debian/control file. The non-native Debian package in the “ 3.0 (quilt) ” format is the most normal Debian source package format.

Each Debian binary package contains the master control file, which contains a number of fields. Each field begins with a tag, ...

If there are no files named preinst , postinst , postrm , or prerm , then that means none of those scripts are part of the Debian packaging.

Each Debian package contains the master `control' file, which contains a number of fields, or comments when the line starts with '#'.