Building OpenSwitch packages¶
Docker-buildpackage supports both interactive and non-interactive package builds.
For this page, assume the following workspace is present.
1 2 | $ git clone https://github.com/open-switch/opx-logging $ git clone https://github.com/open-switch/opx-common-utils |
Non-interactive package builds¶
Build specific repositories by naming them.
1 | $ dbp build opx-logging |
Packages will be deposited in your workspace after a successful build. Use pool-packages to pool packages into per-repository directories for easy sharing.
1 2 3 4 5 | $ ls *.changes
opx-logging_2.1.1_amd64.changes
$ dbp shell -c 'pool-packages *.changes'
$ ls pool/stretch-amd64/opx-logging/*.changes
pool/stretch-amd64/opx-logging/opx-logging_2.1.1_amd64.changes
|
Use dbp build without any arguments to build a full workspace serially. This runs cd $repo; gbp buildpackage for each repository with a debian/control file.
1 | $ dbp build |
The --print-targets flag can be used to preview the build order.
1 2 | $ dbp build --print-targets opx-logging opx-common-utils |
To build in parallel, use the makefile subcommand.
1 | dbp makefile >Makefile && make -j
|
Interactive package builds¶
When developing a package, use dbp run to launch a persistent development container in the background. It can then be entered with dbp shell and removed with dbp rm.
1 2 3 | $ dbp run $ dbp shell $ dbp rm |
Tip
Running dbp build opx-logging is functionally equivalent to
1 | $ dbp shell -c 'cd opx-logging; gbp buildpackage'
|
Running dbp shell launches a Bash session, where the standard Debian workflow is available.
1 2 3 4 5 6 7 8 9 10 11 12 | $ dbp shell build@stretch:/mnt$ cd opx-logging # Install build dependencies and build the package build@stretch:/mnt/opx-logging$ gbp buildpackage # On failed builds, avoid the long gbp build time by quickly rebuilding build@stretch:/mnt/opx-logging$ fakeroot debian/rules binary # Manually clean up build@stretch:/mnt/opx-logging$ fakeroot debian/rules clean build@stretch:/mnt/opx-logging$ exit |
dbp run creates a container based on the current user and directory. To always use the same container name (or start a shell in someone else's), use the --cname environment variable.
1 2 3 4 5 | $ dbp rm Starting container user-dbp-demo... $ dbp --cname DEMO rm Starting container DEMO... |
Debug builds¶
Build unstripped, unoptimized packages with the --debug flag. Both dbp shell and dbp build support it.
1 2 | $ dbp --debug build opx-logging
$ dbp --debug shell -c 'cd opx-logging; gbp buildpackage'
|
Pass additional Git-buildpackage options¶
Use the --gbp flag with dbp build.
1 | dbp build opx-logging --gbp="--git-tag-only" |