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".
9 There 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;
16 1) Create, or have on hand, a local clone of the git repository, with no
17 untracked files or local modifications pending, up-to-date with the branch or
18 commit reference from which you wish to construct the source release.
20 The branch and repository origins will differ based on local conditions.
23 $ git clone -b master ssh://git@example.com:7999/~username/open-vpp
25 ("-b master" can be omitted since master is the default branch)
27 2) Rename the checkout with a version number embedded in its name as is
28 conventional for code releases. Again, your version number may vary.
31 $ mv open-vpp open-vpp-0.0.0
33 3) Ensure that the dpkg-buildpackage program is installed.
37 # apt-get install dpkg-dev
39 4) From the PARENT directory of the debian/ directory, run:
42 $ dpkg-buildpackage -I .git -us -uc
44 (The -us and -uc flags omit GPG signatures from the .dsc and .changes files,
45 respectively. You can add them later, or if you are preparing a signed release
46 and have the signing key on hand, leave off the flags.)
48 5) Get rid of the source directory; you now either have a source package with
49 which you can re-create it at any time, or there were problems with the build,
50 and you should go back to your git checkout to fix them.
52 $ rm -r open-vpp-0.0.0
56 vim:set ai et sw=4 ts=4 tw=80: