summaryrefslogtreecommitdiffstats
path: root/multiple-and-split-binary-packages.txt
blob: 7b19202f258b71006b831333e1036a95049fe91a (plain)
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
PROBLEM CASES
=============

CASE 1: MULTIPLE BINARY PACKAGES
--------------------------------

Some source packages generate multiple binary packages, each of which is built
independently.

Example 1: Linux
The source package for Linux will generate image and headers packages.

Example 2: BusyBox
Some hardware vendors may wish to use a custom BusyBox configuration to better
suit their users' needs.  The source package for BusyBox may generate multiple
builds of BusyBox, each with its own configuration.

CASE 2: SPLIT BINARY PACKAGES
-----------------------------

Some source packages generate multiple binary packages, some or all of which
come from a single build of the packaged software.

Example 1: GCC
The source package for GCC will generate binary packages to provide a C
compiler, support libraries, a C preprocessor, etc.

Example 2: A library with debugging symbols
All binary packages should be stripped of debugging symbols, however many
(especially library) packages may provide debugging symbols (extracted after the
build using objdump) in a separate and optional binary package.