From e879285114995ef31ab7382c885bc9a9d4d7b2cf Mon Sep 17 00:00:00 2001 From: Manoj Srivastava Date: Thu, 16 Jun 2005 05:05:15 +0000 Subject: [PATCH] various Author: srivasta Date: 1999/04/29 19:51:27 various git-archimport-id: srivasta@debian.org--etch/debian-policy--devel--3.0--patch-24 --- packaging.sgml | 123 +++++++++++++++++++++++++++++++++++-------------- 1 file changed, 89 insertions(+), 34 deletions(-) diff --git a/packaging.sgml b/packaging.sgml index 97dcc20..c7d6c14 100644 --- a/packaging.sgml +++ b/packaging.sgml @@ -44,7 +44,26 @@ between dselect and its access method scripts. It does not deal with the Debian Project policy requirements, and it assumes familiarity with dpkg's functions - from the system administrator's perspective. + from the system administrator's perspective. This + package itself is maintained by a group of maintainers + that have no editorial powers. At the moment, the list of + maintainers is: + + +

Michael Alan Dorman mdorman@debian.org

+ + +

Richard Braakman dark@xs4all.nl

+ + +

Philip Hands phil@hands.com

+ + +

Manoj Srivastava srivasta@debian.org

+ + + + Copyright ©1996 Ian Jackson. @@ -118,7 +137,7 @@ This manual describes the technical aspects of creating Debian binary packages (.deb files). It documents the behaviour of the package management programs - dpkg, dselect et al. and and the way + dpkg, dselect et al. and the way they interact with packages.

@@ -853,6 +872,18 @@ information in it to standard output.

+ + dpkg-architecture - + information about the build and host system + + +

+ This program can be used manually, but is also invoked by + dpkg-buildpackage or debian/rules to set + to set environment or make variables which specify the build and + host architecture for the package building process. +

+ The Debianised source tree @@ -875,7 +906,7 @@ tree. They are described below.

- debian/rules - the main building + debian/rules - the main building script @@ -1075,6 +1106,51 @@ either as published or undocumented interfaces or for the package's internal use.

+ +

+ The architecture we build on and build for is determined by make + variables via dpkg-architecture (see ). You can + get the Debian architecture and the GNU style architecture + specification string for the build machine as well as the host + machine. Here is a list of supported make variables: +

+ + + +

DEB_*_ARCH (the Debian architecture)

+ + +

DEB_*_GNU_TYPE (the GNU style architecture + specification string)

+ + +

DEB_*_GNU_CPU (the CPU part of DEB_*_GNU_TYPE)

+ + +

DEB_*_GNU_SYSTEM (the System part of + DEB_*_GNU_TYPE)

+ + +

+ where * is either BUILD for specification of + the build machine or HOST for specification of the machine + we build for. +

+ +

+ Backward compatibility can be provided in the rules file + by setting the needed variables to suitable default + values, please refer to the documentation of + dpkg-architecture for details. +

+ +

+ It is important to understand that the DEB_*_ARCH + string does only determine which Debian architecture we + build on resp. for. It should not be used to get the CPU + or System information, the GNU style variables should be + used for that. +

@@ -1905,7 +1981,7 @@

This is the architecture string; it is a single word for - the CPU architecture. + the Debian architecture.

@@ -1943,30 +2019,9 @@

- The current build architecture can be determined using dpkg - --print-architecture. - -

- This actually invokes - - gcc --print-libgcc-file-name - and parses and decomposes the output and - looks the CPU type from the GCC configuration in a - table in dpkg. This is so that it will - work if you're cross-compiling. -

- This value is automatically used by - dpkg-gencontrol when building the control - file for a binary package for which the source control - information doesn't specify architecture all. + See for information how to get the + architecture for the build process.

- -

- There is a separate option, - --print-installation-architecture, for finding - out what architecture dpkg is willing to - install. This information is also in the output of - dpkg --version.

 Maintainer @@ -2711,7 +2766,7 @@

- It is possible supply scripts as part of a package which + It is possible to supply scripts as part of a package which dpkg will run for you when your package is installed, upgraded or removed.

@@ -3527,7 +3582,7 @@ Dependencies - Depends, Recommends, - tt>Suggett>, Pre-Depends + Suggests, Pre-Depends

@@ -3765,7 +3820,7 @@ Alternative packages - - tt>Conflitt> and Replaces + Conflicts and Replaces

@@ -3840,7 +3895,7 @@ Provides control file field of another package. The effect is as if the package(s) which provide a particular virtual package name had been listed by name - everywhere were the virtual package name appears. + everywhere the virtual package name appears.

@@ -3886,7 +3941,7 @@

If you want to specify which of a set of real packages should be the default to satisfy a particular dependency on a virtual package, you - should list the real package as alternative before the virtual. + should list the real package as an alternative before the virtual.

@@ -3960,7 +4015,7 @@

Secondly, Replaces allows dpkg and dselect to resolve which package should be - removed when a conflict - see . This + removed when there is a conflict - see . This usage only takes effect when the two packages do conflict, so that the two effects do not interfere with each other. @@ -4092,7 +4147,7 @@

If neither the user nor the package maintainer has changed the file, it is left alone. If one or the other has changed - their version, then the changed version is preferred - ie, + their version, then the changed version is preferred - i.e., if the user edits their file, but the package maintainer doesn't ship a different version, the user's changes will stay, silently, but if the maintainer ships a new version -- 2.39.2