blob: db378541371a2e594b746153422981d3089e55d1 (
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
32
33
34
35
36
37
|
PROBLEM CASES
=============
CASE 1: MULTIPLE BINARY PACKAGES
--------------------------------
Some source packages generate multiple binary packages, each of which is built
independently.
The source package format as defined by the current draft specification supports
this case well.
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.
The source package format as defined by the current draft specification does not
support this case.
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.
|
