Isolated Build Environments
Source packages are intended to be buildable on any installation of the target distribution version, provided that build dependencies are met. In addition, builds can be affected by packages already present in the system.
To verify that a package builds on any system, and to exclude any external factors, tools to create isolated build environments are used. These are pbuilder (Personal Builder) and sbuild.
These tools maintain minimal working systems in chroot, install only the necessary build dependencies listed in debian/control, and remove them when the build is finished. Therefore, using pbuilder, a package maintainer can detect if some build dependencies were not specified in debian/control. Also, pbuilder makes it possible to test-build for distributions other than the one the maintainer is running: for example, for the development version, while actually running the stable version.
sbuild is designed for integration with automated build daemons (buildd). It is used by Debian build servers, which automatically build binary packages for every supported architecture. The Launchpad service provides similar build daemons for Ubuntu, both the official distribution and personal package archives (PPAs).
Read more about this topic: Debian Build Toolchain
Famous quotes containing the words isolated, build and/or environments:
“An isolated outbreak of virginity ... is a rash on the face of society. It arouses only pity from the married, and embarrassment from the single.”
—Charlotte Bingham (b. 1942)
“I build only living stones—men.”
—François Rabelais (1494–1553)
“Corporate America will likely be motivated to support child care when it can be shown to have positive effects on that which management is concerned about—recruitment, retention and productivity. Indeed, employers relate to child care as a way to provide growth fostering environments for young managers.”
—Dana E. Friedman (20th century)