1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
-*- Text -*-
List of Build-Essential packages
as of 1999-11-10, Debian potato
Antti-Juhani Kaijanaho
This file lists the non-essential packages that are build-essential.
The list is not closed under the "depends on" relation, so one will
usually need to install more packages than given here.
This list attempts to document the set of build-essential packages as
well as possible. However, it is not authoritative (actually, there
is no authoritative list at all); the definition of the
"build-essential" class of packages given in Debian Policy Manual
(version >= 3.1.0.0), section 2.4 "Source packages" (more precisely
subsection 2.4.2 "Package relationships") is the definitive answer.
Here's the definition (as of Policy 3.1.0.0):
It will not be necessary to explicitly specify build-time
relationships on a minimal set of packages that are always needed
to compile, link and put in a Debian package a standard "Hello
World!" program written in C or C++. The required packages are
called _build-essential_, and an informational list can be found
in `/usr/share/doc/build-essential/list' (which is contained in
the `build-essential' package).
The list is given below in a format which is readable by both man and
machine. The format is described at the end of this file.
BEGIN LIST OF PACKAGES
libc6-dev [!alpha] | libc6.1-dev [alpha] | libc-dev
Provides the ISO C standard library
Indirectly depended on by g++, but we'll ignore
it since libc6-dev is used for non-C++ programs too.
gcc
g++
NOTE:
libstdc++2.10-dev is not needed, as g++ depends on it
make
Also depended on by dpkg-dev, but make does warrant its own
dependency since debian/rules will need it even if dpkg-dev
stopped depending on it
dpkg-dev
Provides dpkg-genchanges and other scripts
NOTE:
Although this list does not contain them, all `Essential: yes'
packages are build-essential as well. A list of such packages
can be found by executing the following command
`grep-status -FEssential -sPackage -ni yes
when the `grep-dctrl' package is installed and in its default
configuration. Such list is installed with this package as
the file
`/usr/share/doc/build-essential/essential-packages-list'
END LIST OF PACKAGES
Here's the format definition:
- First line is the following, without any leading or trailing
whitespace:
BEGIN LIST OF PACKAGES
- Last line is the following, without any leading or trailing
whitespace:
END LIST OF PACKAGES
- A line with leading whitespace is a comment.
- Other lines are joined with end-of-line replaced by comma, and
the result is parsed like the body of the Build-Depends field.
The list of build-essential packages for a particular
architecture is constructed from the result list by ignoring all
the package name - package version pairs which would be ignored
if we were building for that architecture and then removing the
architecture specifications.
The Haskell program list2depends.lhs parses stdin as if it were this
file and outputs one line that is suitable for use in a dependency
field body of a Debian binary package.
|
