blob: b343c78682313531f2d97e10e3c094e432bcbb21 [file] [log] [blame]
Ed Warnickecb9cada2015-12-08 15:45:58 -07001Building DEB packages
2=====================
3
4REQUIREMENTS:
5 You will need a working Internet connection to execute the build, because
6 the build procedure for the included "dpdk" project attempts to contact the
7 Internet host "dpdk.org".
8
9There are three main parts to the process:
10 a) Stage the source tree so that dpkg-source will recognize its organization
11 and create a valid DSC source package for you;
12 b) Ensure that the tools required for building DEB packages are installed;
13 and
14 c) Launch the build.
15
161) Create, or have on hand, a local clone of the git repository, with no
17untracked files or local modifications pending, up-to-date with the branch or
18commit reference from which you wish to construct the source release.
19
20The branch and repository origins will differ based on local conditions.
21
22Example:
23$ git clone -b master ssh://git@example.com:7999/~username/open-vpp
24
25("-b master" can be omitted since master is the default branch)
26
272) Rename the checkout with a version number embedded in its name as is
28conventional for code releases. Again, your version number may vary.
29
30Example:
31$ mv open-vpp open-vpp-0.0.0
32
333) Ensure that the dpkg-buildpackage program is installed.
34
35E.g.,
36
37# apt-get install dpkg-dev
38
394) From the PARENT directory of the debian/ directory, run:
40
41$ cd open-vpp-0.0.0
42$ dpkg-buildpackage -I .git -us -uc
43
44(The -us and -uc flags omit GPG signatures from the .dsc and .changes files,
45respectively. You can add them later, or if you are preparing a signed release
46and have the signing key on hand, leave off the flags.)
47
485) Get rid of the source directory; you now either have a source package with
49which you can re-create it at any time, or there were problems with the build,
50and you should go back to your git checkout to fix them.
51
52$ rm -r open-vpp-0.0.0
53
54END
55
56vim:set ai et sw=4 ts=4 tw=80: