|
|
166.
|
|
|
pbuilder
|
|
|
|
|
pbuilder
|
|
Translated and reviewed by
Donnie Lomat
|
|
|
|
Located in
C/getting_started.xml:84(application)
|
|
|
167.
|
|
|
constructs a chroot system and builds a package inside the chroot. It is an ideal system to use to check that a package has correct build dependencies and to build clean packages to be tested and distributed.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/getting_started.xml:85(para)
|
|
|
168.
|
|
|
Binary and Source Packages
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/getting_started.xml:95(title)
|
|
|
169.
|
|
|
Most users of a Debian-based distribution such as <phrase>Ubuntu</phrase> will never have to deal with the actual source code that is used to create all of the applications on their computers. Instead, the source code is compiled into <emphasis>binary</emphasis> packages from the <emphasis>source</emphasis> package that contains both the source code itself and the rules for making the binary package. Packagers upload the source packages with their changes to the build systems that then compile the binary packages for each architecture. A separate system distributes the generated binary .deb files and source changes to the repository mirrors.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/getting_started.xml:97(para)
|
|
|
170.
|
|
|
The Personal Builder: pbuilder
|
|
|
|
|
Ang Personal Builder: pbuilder
|
|
Translated and reviewed by
menchu lacsamana
|
|
|
|
Located in
C/getting_started.xml:110(title)
|
|
|
171.
|
|
|
Using pbuilder as a package builder allows you to build the package from within a chroot environment. You can build binary packages without using <application>pbuilder</application>, but you must have all the build dependencies installed on your system first. However, pbuilder allows the packager to check the build dependencies because the package is built within a minimal <phrase>Ubuntu</phrase> installation, and the build dependencies are downloaded according to the <filename>debian/control</filename> file.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/getting_started.xml:112(para)
|
|
|
172.
|
|
|
The following is a brief guide to installing, using, and updating a pbuilder environment, however, there are many details of <application>pbuilder</application> usage that are outside the realm of this guide. The <application>pbuilder</application> man page has lots of information and should be consulted if you have problems or need more detailed information.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/getting_started.xml:120(para)
|
|
|
173.
|
|
|
Installing and configuring a pbuilder environment
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/getting_started.xml:128(title)
|
|
|
174.
|
|
|
The first, and perhaps most obvious, thing to do is to install <application>pbuilder</application>. If you want to create a <application>pbuilder</application> for a release newer than the one you currently have installed, you will need to manually install the <application>debootstrap</application> .deb (from <ulink url="http://packages.ubuntu.com">packages.ubuntu.com</ulink>) from the newer release. To create a pbuilder execute:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/getting_started.xml:130(para)
|
|
|
175.
|
|
|
sudo pbuilder create --distribution <distro> \
[tab]--othermirror "deb http://archive.ubuntu.com/ubuntu <distro> universe multiverse"
[tab][tab] |
|
|
[tab] represents a tab character.
Please write it exactly the same way, [tab], in your
translation.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
C/getting_started.xml:139(screen)
|
